From: Joel Soete <soete.joel@tiscali.be>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb: followup
Date: Sat, 21 Feb 2004 19:01:39 +0000 [thread overview]
Message-ID: <4037AB13.3050908@tiscali.be> (raw)
In-Reply-To: <20040218163927.GC9497@baldric.uwo.ca>
Carlos,
Carlos O'Donell wrote:
>>>But now I need more to try to complete job because:
>>>make[2]: *** [/Develop/parisc-linux/build/glibc/sunrpc/xbootparam_prot.stmp]
>
>
> This is the first time that the loader you built is used. If the loader
> is in anyway broke, it will *always* die here first. Just remember this
> glibc haiku when you are coding:
>
> Loader code is bad.
> Dying in sunrpc.
> Blame relocations.
>
> :)
>
It takes me some more time because I would test patch by patch with gcc-3.3 if nothing was broken.
But all those patch seems ok with gcc-3.3 (just have to revert it and re-run with make -k check ;) )
That said, I so have on a system (a n4k runing a 64bit 2.6) a ld.so and libc.so build with gcc-3.5 (let me suffix with (3.5) ie:
ld.so(3.5) and libc.so(3.5)). On another system (a b2k the same 64bit 2.6), I build with gcc-3.3.3 a ld.so(3.3) and libc.so(3.3).
The cmd:
CPP='/Develop/parisc-linux/xc/bin/hppa-linux-gcc -E -x c-header' /Develop/parisc-linux/build/glibc/elf/ld.so.1
--library-path
/Develop/parisc-linux/build/glibc:/Develop/parisc-linux/build/glibc/math:/Develop/parisc-linux/build/glibc/elf:/Develop/parisc-linux/build/glibc/dlfcn:/Develop/parisc-linux/build/glibc/nss:/Develop/parisc-linux/build/glibc/nis:/Develop/p
arisc-linux/build/glibc/rt:/Develop/parisc-linux/build/glibc/resolv:/Develop/parisc-linux/build/glibc/crypt:/Develop/parisc-linux/build/glibc/linuxthreads
/Develop/parisc-linux/build/glibc/sunrpc/rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x
-o /Develop/parisc-linux/build/glibc/sunrpc/xbootparam_prot.T
failled with gcc-3.5
otc ok with gcc-3.3
Now if on the N I replace libc.so(3.5) by libc.so(3.3) the cmd (ie using ld.so(3.5)) always failled
OTC if on the B I replace libc.so(3.3) by libc.so(3.5) the cmd (ie using ld.so(3.3)) works fine.
so it confirms that the loader is broken :(
So I have to figure out what goes wrong in "relocation". Can you help me by pointing out some files and may functions to specialy
analyse :).
Thanks in advance,
Joel
BTW: The previous mentioned patch are (afaik) of general interest (not hppa specific) but would you like that I submit you first
so that you could submit it to glibc maintainers or do you prefer that i manage that myself?
next prev parent reply other threads:[~2004-02-21 19:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 9:22 [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb Joel Soete
2004-02-11 15:32 ` Joel Soete
2004-02-11 16:27 ` Carlos O'Donell
2004-02-11 16:50 ` Joel Soete
2004-02-13 14:35 ` Joel Soete
2004-02-13 19:49 ` Carlos O'Donell
2004-02-14 0:17 ` Grant Grundler
2004-02-14 14:52 ` Joel Soete
2004-02-14 18:23 ` Carlos O'Donell
2004-02-14 19:29 ` Joel Soete
2004-02-16 17:31 ` Joel Soete
2004-02-17 21:10 ` Carlos O'Donell
2004-02-18 13:16 ` Joel Soete
2004-02-18 13:36 ` Elliott Potter
2004-02-18 14:42 ` Joel Soete
2004-02-18 16:39 ` Carlos O'Donell
2004-02-18 17:25 ` Joel Soete
2004-02-18 18:40 ` Joel Soete
2004-02-21 19:01 ` Joel Soete [this message]
2004-02-22 6:00 ` [parisc-linux] glibc-2.3.3 & gcc-snapshot (3.5.0) pb: followup Carlos O'Donell
2004-02-22 16:53 ` John David Anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4037AB13.3050908@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=carlos@baldric.uwo.ca \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox