[FFmpeg-devel] [PATCH] List enabled code in configure output

Rich Felker dalias
Tue Sep 25 21:46:31 CEST 2007

On Tue, Sep 25, 2007 at 07:02:37PM +0100, M?ns Rullg?rd wrote:
> > Ok, I'll try again with: mans --verbose 2 ./configure
> >
> > Could you enlighten us where it's not POSIX compatible?
> The ${space:0:$length} and ${*//$suffix/} substitutions are not POSIX
> compatible.
> > It ran fine with bash --posix, in bash with set -o posix as the first 
> > command, and with ksh too. Actually ksh bugged (Terminated) on 
> > check_exec_crash, but that's a separate issue.
> Bash POSIX mode apparently does not necessarily complain about
> extended features.  I'm guessing it only changes behaviour when there
> is a direct conflict with POSIX.

Next time try using ash (from busybox), dash (from Debian), ksh, posh,
or similar for testing. Bash is really bad about these sorts of
things. Ideally distributions would make /bin/sh a symlink to a real
posix shell so bugs like this would be immediately caught, but sadly
they don't for the sake of supporting buggy user scripts.


P.S. Yes such nonportable scripts are buggy because if they depend on
bash behavior they should have #!/bin/bash instead of #!/bin/sh

More information about the ffmpeg-devel mailing list