From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] --build-id= none in newer ld versions PowerPC
Date: Tue, 02 Dec 2008 13:34:17 -0500 [thread overview]
Message-ID: <1228242857.32248.16.camel@dv> (raw)
In-Reply-To: <49356D02.4060201@nic.fi>
On Tue, 2008-12-02 at 19:14 +0200, Vesa Jääskeläinen wrote:
> No no. I mean just KERNEL_LDFLAGS like comparison to MODULE_LDFLAGS. No
> elf or nothing like that. Is there any problem if one provides this
> setting even on x86 if linker recognizes it? (what is being tested
> here). PPC_BUILD_ID_FLAG just sounds too specific.
>
> Isn't EFI also using ELF? I assume this would be beneficial also there.
I agree, we should not be be multiplying hacks. There is already code
adding -Wl,--build-id=none to TARGET_LDFLAGS. It's a macro
grub_PROG_LD_BUILD_ID_NONE in aclocal.m4. What's wrong with it? Does
it fail to add -Wl,--build-id=none on PowerPC or is TARGET_LDFLAGS not
used to link kernel.elf?
What are the symptoms caused by not using -Wl,--build-id=none?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-12-02 18:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 16:51 [PATCH] --build-id= none in newer ld versions PowerPC Manoel Rebelo Abranches
2008-12-01 17:01 ` Vesa Jääskeläinen
2008-12-01 17:34 ` Manoel Rebelo Abranches
2008-12-02 17:14 ` Vesa Jääskeläinen
2008-12-02 18:34 ` Pavel Roskin [this message]
2008-12-02 19:16 ` Manoel Rebelo Abranches
2008-12-04 14:08 ` Manoel Rebelo Abranches
2008-12-11 11:51 ` Manoel Rebelo Abranches
2009-01-05 6:38 ` Jerone Young
2009-01-05 6:53 ` Pavel Roskin
2009-01-05 7:09 ` Jerone Young
2009-02-07 19:50 ` Robert Millan
2009-02-08 17:09 ` Gregg C Levine
2009-04-01 16:11 ` Pavel Roskin
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=1228242857.32248.16.camel@dv \
--to=proski@gnu.org \
--cc=grub-devel@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: 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.