[Ffmpeg-devel] [PATCH] Move BeOS-specific code into os_support.c

[Måns Rullgård]

Michael A. Kohn said:
>
>
> On Tue, 14 Nov 2006, M?ns Rullg?rd wrote:
>
>>
>> Michael A. Kohn said:
>>
>>> Also in the configure script, the first set of lines under "make sure we
>>> are running under a compatible shell" have to be commented out to work on
>>> BeOS and MingW compiled under MSys on Windows.
>>
>> Those tests are there for a reason.  If they fail, the configure script will
>> not work properly.
>>
>> --
>> M?ns Rullg?rd
>> mru at inprovide.com
>
> Could be.  The configure script seems to work fine after commenting out
> those lines tho.

It may appear to run correctly.  However, some of the tests will silently give
wrong results.

> What's interesting is msys doesn't even include a "bash.exe" but instead
> has an sh.exe (and I'm 99% sure BeOS was the same.. I had to make a
> symbolic link from sh to bash).. when I type sh --version on Msys it
> says: GNU bash, version 2.04.0(1)-release (i686-pc-msys)..

That version of bash is known to be broken.

> I believe BeOS did the same thing.. sh is really bash under a new name..
>
> If I copy sh.exe to bash.exe (and even the symbolic link on BeOS from sh
> to bash) the configure script says: "No compatible shell script
> interprerter found."

Your only way out is to install a compatible shell.  A newer version of bash
will work, as will ksh or any other POSIX compliant shell.

-- 
M?ns Rullg?rd
mru at inprovide.com