[Ffmpeg-devel] [PATCH] AVISynth support

[Steve Lhomme]

Diego Biurrun wrote:
> On Thu, Aug 17, 2006 at 12:29:18PM +0200, Steve Lhomme wrote:
>> Diego Biurrun wrote:
>>> On Wed, Aug 16, 2006 at 11:45:07PM +0200, Steve Lhomme wrote:
>>>> For some reason it doesn't add -lvfw32 to EXTRALIBS, but since it 
>>>> doesn't add it for -lz either I guess the SVN is broken under MSys. MSys 
>>>> doesn't use bash by default (which seem to be a new requirement in 
>>>> FFMPEG).
>>> Huh?  Since when do we require bash?  What is the problem?
>> When I run the SVN configure script in MSys (that I never had a problem 
>> with during the last 6 months), I get this error:
>>
>> Steve at LAPUX4 /C/Perso/Programmes/ffmpeg.svn
>> $ ./configure
>> ./configure: exec: bash: not found
>>
>> It is caused by these lines at the beggining of the configure script:
>>
>> unset foo
>> (: ${foo%%bar}) 2>/dev/null && ! (: ${foo?}) 2>/dev/null
>> if test "$?" != 0; then
>>     if test "x$FFMPEG_CONFIGURE_EXEC" = x; then
>>         FFMPEG_CONFIGURE_EXEC=1
>>         export FFMPEG_CONFIGURE_EXEC
>>         exec bash "$0" "$@"
>>         exec ksh "$0" "$@"
>>         exec /usr/xpg4/bin/sh "$0" "$@"
>>     fi
>>     echo "No compatible shell script interpreter found."
>>     exit 1
>> fi
> 
> These lines test the shell for compatibility.  What shell are you using
> in MSys if not bash?

$ /bin/sh.exe --version
GNU bash, version 2.04.0(1)-release (i686-pc-msys)
Copyright 1999 Free Software Foundation, Inc.

If I change the script to try sh it gives the error "No compatible shell 
script interpreter found.". So I guess the bash shell in MSys is not 
compatible ?

>> I don't know if that fact that I don't have bash is the reason why -lz 
>> and -lvfw32 are not added to EXTRALIBS. (I removed these lines so that I 
>> can use the configure script).
> 
> Have you looked at config.err?  The reason is probably that your shell is
> not able to run 
> 
>   flags_saved(){ (: ${SAVE_CFLAGS?}) 2>/dev/null }

config.err doesn't give any error about saving flags. They are just not 
stored (but detected correctly).

Steve