From: "Kris Warkentin" <kewarken@qnx.com>
To: <binutils@sources.redhat.com>
Subject: Re: ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1?
Date: Fri, 28 Nov 2003 18:21:00 -0000 [thread overview]
Message-ID: <089b01c3b5dc$a0e32860$0202040a@catdog> (raw)
I asked this on the gcc mailing list but they suggested to ask binutils.
In the course of building some powerpc startup code we found ld complaining
about "allocated section `.rodata.str1.4' not in segment" and "allocated
section `.eh_frame' not in segment". I observed that some of the objects in
the startup had .rodata.str1.4 sections in them. I also observed that if I
took the ld from binutils 2.12.1 to 2.14, the problem went away.
I didn't find any talk of a hard binutils requirement for the 3.3 series of
gcc but perhaps I missed it. Can anyone shed some light on this? I hope
I'm not too astonishing in my ignorance but this .rodata.str1.x doesn't seem
to be generated by our older gcc and I don't really know what the
significance of it all is.
Essentially we're in the middle of a release and are stuck at our current
gcc and binutils versions for the moment so if anyone can give me an idea of
how to understand/work around the problem, I'd be very grateful.
cheers,
Kris
next reply other threads:[~2003-11-28 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 18:21 Kris Warkentin [this message]
[not found] <087e01c3b5da$77d658e0$0202040a@catdog>
2003-11-29 1:42 ` Alan Modra
2003-11-29 18:14 ` Kris Warkentin
[not found] ` <amodra@bigpond.net.au>
2003-11-29 2:33 ` David Edelsohn
2003-11-29 3:05 ` Alan Modra
2003-11-29 4:06 ` David Edelsohn
2003-11-29 4:10 ` Andrew Pinski
2003-11-29 4:20 ` David Edelsohn
2003-11-29 6:47 ` Alan Modra
2003-11-29 19:40 ` David Edelsohn
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='089b01c3b5dc$a0e32860$0202040a@catdog' \
--to=kewarken@qnx.com \
--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).