GCC3 and Solaris
james at xemacs.org
Fri Feb 11 15:40:46 EST 2005
Vin Shelton <acs at xemacs.org> wrote:
> Frank Jensen <Frank.Jensen at hugin.com> writes:
> IIRC, this option is no longer needed. We fixed the aliasing problems
> some time ago in the 21.4 code base.
Errrrr.... Did we? There are still several aliasing problems in 21.5.
>> > Compiler version: gcc (GCC) 3.4.3
>> Hmm. My output says:
>> Compiler version: gcc: `-V' option must have argument
>> Are you using modified source code?
> Nope. Jerry put the ability to check compiler version in awhile ago.
> My build script specifies a compiler of CC=gcc; I wonder if that makes a
Who, moi? I contributed the checker for icc and icpc last April, but
the general framework was put together by Valdis Kletnieks, was it not?
In any case, the info docs for gcc 3.4 say that the -V flag is to run a
specific version of gcc. To get the version, you're supposed to use
--version. In fact, that's what configure.in *is* using for gcc. It
looks like the logic starting at the line that says:
AC_MSG_CHECKING(for compiler version information)
must be slightly awry for Frank's case. The test:
if test "$GCC" = "yes"; then
must be failing for Frank, dropping him into the machine-specific code,
which results in this code being executed:
compiler_version=`$XEMACS_CC -V 2>&1 | head -1`
Frank, are you passing either --compiler or --xemacs-compiler to the
configure script? Do you have CC set in your environment? If so, what
More information about the XEmacs-Beta