Are there any autoconf gurus out there that can figure out why mad can't handle certain CFLAGS invocations properly?
For example, try the following in the mad-0.12.2b source directory:
$ env CFLAGS="-O1 -O2" ./configure
configure will eventually crash with something like this:
checking for gcc... (cached) gcc checking whether the C compiler (gcc 2 ) works... no configure: error: installation or configuration problem: C compiler cannot create executables. configure: error: ./configure failed for libmad
Removing the first `-O1' fixes it, but this should not be necessary since gcc should pick up the latter.
From gcc(1):
"If you use multiple -O options, with or without level numbers, the last such option is the one that is effective."
Further, this isn't a problem on several other autoconf driven packages I tested this with.
Thanks.