From: Hollis Blanchard <hollisb@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: openbios@openbios.org
Subject: Re: [OpenBIOS] [Qemu-devel] Re: building openbios-qemu.elf?
Date: Tue, 24 Feb 2009 10:44:54 -0600 [thread overview]
Message-ID: <1235493894.6429.53.camel@slate.austin.ibm.com> (raw)
In-Reply-To: <5264924.442961235493077105.JavaMail.servlet@kundenserver>
On Tue, 2009-02-24 at 17:31 +0100, Laurent Vivier wrote:
> >On Tue, 2009-02-24 at 00:07 +0100, Laurent Vivier wrote:
> >> Hi,
> >>
> >> Do you use source from SVN head ?
> >
> >Yes.
> >
> >> Do you have any information in obj-ppc/build.log ?
> >
> >This is somewhat interesting:
> >
> >powerpc-440-linux-gnu-strip openbios-qemu.elf
> >BFD: st4PszLi: warning: allocated section `.bss' not in segment
> >BFD: st4PszLi: warning: allocated section `.sbss' not in segment
> >
> >The "nostrip" version of openbios-qemu.elf looks much better:
> >
> >Program Headers:
> > Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
> > LOAD 0x000094 0xfff00000 0xfff00000 0x42044 0x4bcb4 RWE 0x4
> > LOAD 0x0420d8 0xfffffffc 0xfffffffc 0x00004 0x00004 R E 0x1
> > GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RWE 0x4
> >
> > Section to Segment mapping:
> > Segment Sections...
> > 00 .text.vectors .text .rodata .data .sdata
> > 01 .romentry
> > 02
> >
> >So something goes wrong in the strip process.
> >
>
> What is the version of your binutils ?
> (I use 2.18.0.20080103)
2.16.1
> You can also try the native strip of your host if you have installed
> binutils-multiarch (for a debian system).
I don't know of anything like that for Fedora, and the native strip
supports only x86 variants.
--
Hollis Blanchard
IBM Linux Technology Center
prev parent reply other threads:[~2009-02-24 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 16:31 [OpenBIOS] [Qemu-devel] Re: building openbios-qemu.elf? Laurent Vivier
2009-02-24 16:44 ` Hollis Blanchard [this message]
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=1235493894.6429.53.camel@slate.austin.ibm.com \
--to=hollisb@us.ibm.com \
--cc=openbios@openbios.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).