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] |
On 2004-07-08 at 17:21:26 Dan Kegel wrote: >> patches/glibc-linuxthreads-2.3.2/glibc-linuxthreads-2.3.2-allow-3.4.patch > No, he's building glibc-2.2.5, not 2.3.2. Maybe we need a similar patch for 2.2.5? > But I don't think so; here, powerpc-405 / gcc-3.4.1-glibc-2.2.5 bulds just fine I just posted a similar patch for 2.2.5. Maybe this specific build error is only triggered by using -O2 or -Os? This causes various problems for initfini.c-derived stuff, using gcc 3.4.x. > Odd - mipsel builds fine here with gcc-3.4.1 and glibc-2.3.2 as > currently patched. I don't seem to need to extend the patch. Sorry if I was unclear, I basically copy/pasted the mips stuff to powerpc, but didn't modify mips at all. > Can either of you give me a recipe for reproducing the > problem on mipsel or ppc405 using vanilla crosstool-0.28-rc28? I'd guess trying to put -O2 or -Os in TARGET_CFLAGS. > I think I just took the patch directly from glibc cvs. I prefer > doing it their way when possible. Have you checked to see > if they addressed your issues in glibc cvs? If so, I'd > prefer to take their change. (If not, maybe you need to > submit the change to them?) I'll look into this...
Attachment:
pgp00000.pgp
Description: PGP signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |