public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Glaser <tg@66h.42h.de>
To: binutils@sources.redhat.com
Subject: Re: cvs binutils+gcc4.0 build fail
Date: Tue, 29 Mar 2005 23:33:00 -0000	[thread overview]
Message-ID: <Pine.BSO.4.61L.0503291905300.11002@odem.66h.42h.de> (raw)
In-Reply-To: <20050329110741.GK14407@bubble.modra.org>

Alan Modra dixit:

>On Tue, Mar 29, 2005 at 04:21:39PM +0930, Alan Modra wrote:
>> Something was indeed going wrong with eh_frame editing.  It was being
>> done twice due to my 2005-03-21 ppc64elf.em change.  Oops.
>
>Blah, it's worse than that.  .eh_frame needs to be edited before stubs
>and suchlike are built.  If the section layout changes after we're done
>adding stubs, then some of the stubs will have incorrect offsets.

I've got a similar problem; just applying your emultempl/elf32.em diff
on top of a binutils-20050328 snapshot didn't help :-(

This is gcc-3.4.4 (20050325).


tg@odem:/home/tg $ g++ -static x.cc
/usr/bin/ld: `.gnu.linkonce.t._ZNKSt5ctypeIcE13_M_widen_initEv' referenced in section `.data' of /usr/lib/libstdc++.a(locale-inst.o): defined in discarded section `.gnu.linkonce.t._ZNKSt5ctypeIcE13_M_widen_initEv' of /usr/lib/libstdc++.a(locale-inst.o)

/usr/bin/ld: `.gnu.linkonce.t._ZStneIcSt11char_traitsIcESaIcEEbRKSbIT_T0_T1_EPKS3_' referenced in section `.data' of /usr/lib/libstdc++.a(locale_init.o): defined in discarded section `.gnu.linkonce.t._ZStneIcSt11char_traitsIcESaIcEEbRKSbIT_T0_T1_EPKS3_' of /usr/lib/libstdc++.a(locale_init.o)

tg@odem:/home/tg $ ./a.out
Segmentation fault (core dumped)
tg@odem:/home/tg $ cat x.cc
#include <iostream>
using namespace std;
main() { cout << "Hello, World!" << endl; }
tg@odem:/home/tg $ uname -a
MirBSD odem.66h.42h.de 8 Kv#8n24-20050315 GENERIC#660 i386


Do you have an idea if this is a binutils or a gcc problem?

Thanks in advance,
//mirabile, who doesn't know C++ but got the task to port it to MirOS

PS: Yes, this target isn't supported (yet) in stock binutils,
    but I've got my papers done, just got no time to split our
    diff up into smaller pieces and feed back.
-- 
> [...] Echtzeit hat weniger mit "Speed"[...] zu tun, sondern damit, daß der
> richtige Prozeß voraussagbar rechtzeitig sein Zeitscheibchen bekommt.
Wir haben uns[...] geeinigt, dass das verwendete Echtzeit-Betriebssystem[...]
weil selbst einfachste Operationen *echt* *Zeit* brauchen.	(aus d.a.s.r)

  reply	other threads:[~2005-03-29 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050322212341.GD4980@krispykreme>
     [not found] ` <20050323083219.A21240@mailhub.air.net.au>
     [not found]   ` <20050322222308.GE30711@bubble.modra.org>
2005-03-29 13:54     ` Alan Modra
2005-03-29 15:43       ` Alan Modra
2005-03-29 23:33         ` Thorsten Glaser [this message]
2005-03-30 16:34           ` Alan Modra

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=Pine.BSO.4.61L.0503291905300.11002@odem.66h.42h.de \
    --to=tg@66h.42h.de \
    --cc=binutils@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).