[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compiling M4-1.4.10
Re: Compiling M4-1.4.10
Tue, 07 Aug 2007 18:35:19 -0600
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20070728 Thunderbird/188.8.131.52 Mnenhy/0.7.5.666
-----BEGIN PGP SIGNED MESSAGE-----
According to STEVE555 on 8/7/2007 5:03 PM:
> First of all yes that was the patch I was referring to,I'm sorry I had no
> idea it was for the CVS version of M4.The M4 I'm compiling with is form the
> tarball sorurce from GNU.
It seems a little bit inconsistent that you want bleeding-edge unreleased
gcc, but are willing to stick with the 1.4.10 tarball rather than going
with CVS, but I suppose that's okay.
> Second,the O.S I'm using is Linux Kubuntu Feisty Fawn version 7.04.
> Third, the config.log is here:
> http://www.nabble.com/file/p12044224/config.log config.log .
Thanks. Obviously, we currently don't do a good job of detecting outdated
system headers in the presence of bleeding edge compilers.
> Fourth,the GCC version is 4.3.0 from the SVN repository.I had applied the
> updates for it and re-compiled it yesterday.
Bingo - just as I guessed. You need to upgrade your glibc installation
before you can use gcc 3.4.x:
> 5th,Here is my wchar.h : http://www.nabble.com/file/p12044224/wchar.h
Just as I thought - you have an old header where wcstouq is still declared
A word of advice - there is nothing inherently wrong with using
bleeding-edge unreleased tools (such as the gcc 4.3.0 svn snapshot); after
all, somebody has to test it before it can be released as a stable
product. However, using unreleased software is something that generally
takes an extreme amount of experience and knowledge, not to mention a
close monitoring of the development mailing lists, so that changes in
behavior will not be a total surprise to you. The fact that you reported
your problem to the m4 list, rather than the gcc or glibc lists, shows
that you probably aren't prepared for bleeding edge gcc development yet.
If it were me, I would downgrade your gcc back to the pre-compiled 4.2.x
shipped with your distro, rather than trying to use an unreleased gcc 4.3;
when 4.3 is finally released, I would then wait until Kubuntu releases it
as a precompiled package, because then you will be guaranteed to also pick
up any prerequisite upgrades such as system headers. But if you plan on
continuing with gcc 4.3 right now, then it is not m4's bug that you can't
compile; rather, it is the mismatch between your outdated system headers
and your new compiler.
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----