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

Diego Biurrun diego
Tue Nov 14 16:51:10 CET 2006


On Tue, Nov 14, 2006 at 09:04:19AM -0600, Michael A. Kohn wrote:
> 
> On Tue, 14 Nov 2006, M?ns Rullg?rd wrote:
> 
> >Michael A. Kohn said:
> >>
> >>On Tue, 14 Nov 2006, M?ns Rullg?rd wrote:
> >>
> >>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.
> 
> WOW.  You were so right.  I updated to bash 2.05b on Msys and now the 
> configure script works *AND* compiler error I wrote about earlier went
> away.  It now builds just fine under MSYS.

Reading the FAQ does pay off, you know ;)

Diego




More information about the ffmpeg-devel mailing list