Matti Rintala wrote: > It's not the RedHat people, it's the gcc project itself. I've built my > 3.1 from original gcc sources and it reports the version in the > following way: > > [bitti]$ /usr/local/gcc-3.1/bin/gcc --version > gcc (GCC) 3.1 > Copyright (C) 2002 Free Software Foundation, Inc. > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > So the RedHat only added their own build information.
You're right. I opened a bugreport at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65598 on the issue, and the RedHat people told me the same. The conclusion is that all the following construct does _not_ work in configure.in to check for gcc version 3.x: GCC_version=`${CC} --version` ... case "${GCC_version}" in 2.96*) # 2.96 specific stuff, works fine as # gcc --version returns the string "2.96" 3.*) # this branch never gets control as gcc 3.x # returns "gcc (GCC) 3.x ..." *) # this is where gcc 3.x goes as well esac The new version string is in accordance with new GNU coding guidelines, see http://www.gnu.org/prep/standards_18.html#SEC18 . Unfortunately the new style of version string is not well defined in terms of parsing. Anyway, the RedHat guy suggested using the following expression for telling the gcc version number: gcc --version | sed -n '1s/^[^ ]* (.*) //;s/ .*$//;1p' this one works for me for gcc 2.96 and 3.1. Thus replacing line 94: GCC_version=`${CC} --version` with GCC_version=`${CC} --version | sed -n '1s/^[[^ ]]* (.*) //;s/ .*$//;1p'` does the trick. Akos _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
