public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@ens.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10805: [sun-solaris2.7] relocation error when creating sparcv9/libgcc_s.so.1 Date: Fri, 16 May 2003 13:16:00 -0000 [thread overview] Message-ID: <20030516131600.11750.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10805; it has been noted by GNATS. From: Marc Glisse <marc.glisse@ens.fr> To: ebotcazou@gcc.gnu.org, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <glisse@mmfai.ens.fr>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: bootstrap/10805: [sun-solaris2.7] relocation error when creating sparcv9/libgcc_s.so.1 Date: Fri, 16 May 2003 15:12:34 +0200 (MET DST) On 16 May 2003 ebotcazou@gcc.gnu.org wrote: > I can't reproduce on SunOS vegeta 5.7 Generic_106541-23 sun4u sparc SUNW,Ultra-2 > with cc: Sun WorkShop 6 update 2 C 5.3 Patch 111679-08 2002/05/09 > as the bootstrap compiler. One difference is that I do not have this patch. I will try to install it as soon as I can. For the bootstrap compiler, I used: cc: Sun WorkShop 6 2000/04/07 C 5.1 gcc (GCC) 3.2.2 And both give the same result. > Could you determine at which stage bootstrap fails? > If the compiler's C source files were latterly compiled by cc, it's stage1. > If they were compiled by stage1/xgcc, it's stage2 and if they were > compiled by stage2/xgcc, it's stage3. first there is a lot of gcc. Then this gcc/xgcc. Actually this should be clearer: make[3]: *** [sparcv9/libgcc_s_sparcv9.so] Error 1 make[3]: Leaving directory `/global/lavarenne/download/gcc-3.3/gcc' make[2]: *** [stmp-multilib] Error 2 make[2]: Leaving directory `/global/lavarenne/download/gcc-3.3/gcc' make[1]: *** [stage1_build] Error 2 make[1]: Leaving directory `/global/lavarenne/download/gcc-3.3/gcc' make: *** [bootstrap] Error 2 > And could you post the ouput of 'dump -r _muldi3.o'? _muldi3.o: **** RELOCATION INFORMATION **** .rela.debug_info: Offset Symndx Type Addend 0x6 3 23 0 0xc 9 3 0 0x10 6 32 152 0x18 6 32 0 0x3ee 2 23 12 0x48c 2 3 12 0x122f 2 23 0 0x123d 2 23 30 0x1375 2 23 0 0x1383 2 23 30 0x163e 2 23 39 0x1654 2 3 39 0x172f 6 54 0 0x1737 6 54 152 0x1786 6 54 28 0x178e 6 54 120 0x17a7 6 54 28 0x17af 6 54 120 .rela.debug_line: Offset Symndx Type Addend 0x139 6 54 0 0x148 6 32 8 0x154 6 54 12 0x160 6 32 16 0x16c 6 54 28 0x178 6 32 116 0x184 6 54 128 0x190 6 32 132 0x19c 6 54 136 0x1a8 6 32 140 0x1b4 6 54 144 0x1c0 6 32 152 .rela.debug_frame: Offset Symndx Type Addend 0x1c 7 3 0 0x20 6 32 0 .rela.debug_pubnames: Offset Symndx Type Addend 0x6 4 23 0 .rela.debug_aranges: Offset Symndx Type Addend 0x6 4 23 0 0x10 6 32 0 With the messages: ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: symbol <unknown>: offset 0xffffffff7ec133e7 is non-aligned ld: fatal: relocation error: R_SPARC_64: file libgcc/sparcv9/_muldi3.o: symbol <unknown>: offset 0xffffffff7ec133eb is non-aligned ld: fatal: relocation error: R_SPARC_64: file libgcc/sparcv9/_muldi3.o: symbol <unknown>: offset 0xffffffff7ec133f3 is non-aligned ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: symbol <unknown>: offset 0xffffffff7ec13867 is non-aligned ld: fatal: relocation error: R_SPARC_32: file libgcc/sparcv9/_muldi3.o: symbol <unknown>: offset 0xffffffff7ec14a2f is non-aligned But about all the .o give this kind of messages. The first thing I will do is get a patch cluster for solaris2.7.
next reply other threads:[~2003-05-16 13:16 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-16 13:16 Marc Glisse [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 8:57 ebotcazou 2003-05-20 18:46 Marc Glisse 2003-05-20 12:08 Eric Botcazou 2003-05-20 11:26 Marc Glisse 2003-05-20 10:56 Eric Botcazou 2003-05-17 7:06 Eric Botcazou 2003-05-17 6:42 ebotcazou 2003-05-17 1:16 Dara Hazeghi 2003-05-16 22:26 Eric Botcazou 2003-05-16 15:16 Eric Botcazou 2003-05-16 13:06 Eric Botcazou 2003-05-16 10:08 ebotcazou 2003-05-15 17:06 glisse
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=20030516131600.11750.qmail@sources.redhat.com \ --to=marc.glisse@ens.fr \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).