Alexander Leidinger wrote:
> The possible values are "full", "norm", "yes" and "no". "yes" is the
> same as "norm". So I just don't tell the people about "yes". This is
> intended, because "full" and "norm" describe the possibilities IMHO
> better (and I added "yes" just as a fail safe behavior).
not quite so.
when trying:
./configure --enable-expopt=full
I get:
checking for additional optimizations... configure: error: bad value
�full� for expopt option
looking at the configure script, it seems that one of the case
statements is not closed inside the full branch for this option. in
particular the case starting at line 633:
case "${GCC_version}" in
2.9*|3.*)
contains only this one choice, and is not closed by an esac statement.
(also, there is no default branch for this case, which is unfortunate)
Akos
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
