From: David Miller <davem@davemloft.net>
To: grub-devel@gnu.org, okuji@enbug.org
Subject: Re: [PATCH]: grub: Allow to control objcopy '-B' argument from foo.rmk files.
Date: Sat, 11 Apr 2009 04:46:44 -0700 (PDT) [thread overview]
Message-ID: <20090411.044644.82196010.davem@davemloft.net> (raw)
In-Reply-To: <200904111923.23652.okuji@enbug.org>
From: "Yoshinori K. Okuji" <okuji@enbug.org>
Date: Sat, 11 Apr 2009 19:23:23 +0900
> On Saturday 11 April 2009 17:08:31 David Miller wrote:
>> This patch allows a platform to specify the image file output
>> format, it also adds the --strip-unneeded option to the objcopy
>> invocation as well.
>
> IIRC, --strip-unneeded was dangerous.
I would like to have information about this :-)
We do want to retain symbols (and potentially even debugging
information) in the foo.exec files. But the final images are pure
binary blobs and there is no real use for any of the symbol
information.
In fact, the the way i386 uses this, it outputs "binary" format
images. I can't even think of where it would place any symbol
tables :-)
On sparc64 this will actually matter, because we need to use
a.out format images for the boot blocks. If I leave the symbols
in there, this brings the boot block over it's required 512-byte
size.
>> I've left the i386-pc.mk portion of this patch out of the posting,
>> but rest assured I will check that part in once this gets an ACK :-)
>
> I don't like "IMG_FMT". How about "FORMAT"? If too ambiguous, "IMAGE_FORMAT".
> I prefer not to use uncommon abbrevs.
That's fine with me, I'll update the patch once the strip issue
is resolved.
next prev parent reply other threads:[~2009-04-11 11:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 8:08 [PATCH]: grub: Allow to control objcopy '-B' argument from foo.rmk files David Miller
2009-04-11 10:23 ` Yoshinori K. Okuji
2009-04-11 11:46 ` David Miller [this message]
2009-04-13 6:38 ` David Miller
2009-04-13 14:29 ` Robert Millan
2009-04-13 20:33 ` David Miller
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=20090411.044644.82196010.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grub-devel@gnu.org \
--cc=okuji@enbug.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.