This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC trivia question


Peter Barada wrote:
Nope... not if you want to build later versions
of glibc.  Believe it or not, glibc cvs requires gcc-4.0!

Strike that. Reverse it. The only version of glibc that officially supports gcc-4.0 is glibc cvs. (crosstool-0.32 has patches to build older glibc's with gcc-4.0, though.)

I should simply have pointed to the glibc doc
http://www.gnu.org/software/libc/FAQ.html
--- snip ---
1.2. What compiler do I need to build GNU libc?
{UD} You must use GNU CC to compile GNU libc.
A lot of extensions of GNU CC are used to increase portability and speed...
You should always try to use the latest official release.
Older versions may not have all the features GNU libc requires.
The current releases of gcc (3.2 or newer) should work with the GNU C library (for MIPS see question 1.20).

Please note that gcc 2.95 and 2.95.x cannot compile glibc on Alpha due to problems in the complex float support.

1.20. Which tools should I use for MIPS?
{AJ} You should use the current development version of gcc 3.2 or newer from CVS.

You need also recent binutils, anything before and including
2.11 will not work correctly.
Either try the Linux binutils 2.11.90.0.5 from HJ Lu or
the current development version of binutils from CVS. ...

1.21. Which compiler should I use for powerpc64?
{SM} You want to use at least gcc 3.2 (together with the right versions of all the other tools, of course).
--- snip ---

Will glibc-2.3.5 build with gcc-3.4.3?

I find that I need patches to build glibc-2.3.5 with *any* gcc. Which patches depend on which CPU type. I imagine you're interested in m68k. That fails at the moment with

../sysdeps/generic/wordexp.c: In function `exec_comm':
../sysdeps/generic/wordexp.c:815: sorry, unimplemented: inlining failed in call to 'exec_comm_child': function body not available
../sysdeps/generic/wordexp.c:900: sorry, unimplemented: called from here
make[2]: *** [/home/dkegel/queue/jobdir.produser_cpsm16/crosstool-0.32/build/m68k-unknown-linux-gnu/gcc-3.4.3-glibc-2.3.5/build-glibc/posix/wordexp.o] Error 1

which might be fixed by

http://www.kegel.com/crosstool/current/patches/glibc-2.3-20050307/glibc-2.3.4-allow-gcc-4.0-wordexp.patch

If you're building with crosstool-0.31, you'll probably also need
http://www.kegel.com/crosstool/current/patches/glibc-2.3-20050307/make-install-lib-all.patch
to get around the libeh problem.

And there may be other little issues.  I'll try to clean them up for crosstool-0.32,
at least for a couple cpu types.
- Dan

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]