This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

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: GLIBC 2.3.3 build failure on i686-pc-linux-gnu

From: James E Wilson <wilson at specifixinc dot com>
To: Sam Lauber <sam124 at operamail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 10 Nov 2004 20:27:54 -0800
Subject: Re: GLIBC 2.3.3 build failure on i686-pc-linux-gnu
References: <20041110010143.2CAF523CE7@ws5-3.us4.outblaze.com>

Sam Lauber wrote:

/home/sam/build-glibc/csu/crtn.o(.text+0x0): In function `dummy':
/home/sam/build-glibc/csu/crtn.S:14: multiple definition of `dummy'

We don't maintain glibc here, but this might be the unit-at-a-time problem. Try compiling csu/initfini.c (or whatever is used to generate the csu/crt* files) with -fno-unit-at-a-time.

There is often a close tie between glibc and gcc releases, because of interdependencies between them. As a result, you should not assume that any gcc release can compile any glibc release. Sometimes, there is only one gcc release than can correctly compile a particular glibc release. However, since we don't do glibc here, I can't give you more details on this. You would have to ask on a glibc list.

You could try looking for people that have collected gcc/glibc patches. Any linux release will have compatible gcc/glibc. Dan Kegel's crosstool scripts have compatible gcc/glibc. See http://kegel.com/crosstool -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

References:
- GLIBC 2.3.3 build failure on i686-pc-linux-gnu
  - From: Sam Lauber

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