public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Fangrui Song <maskray@google.com>
To: Sam James <sam@gentoo.org>
Cc: libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] Makerules: Generate shlib.lds with -fuse-ld=bfd
Date: Sun, 6 Nov 2022 15:06:57 -0800	[thread overview]
Message-ID: <CAFP8O3+=Fb_cN-de8+JuksVSk1u6ZEaYdDZKBNPfF10hkO_2cQ@mail.gmail.com> (raw)
In-Reply-To: <5D161B01-124A-48A5-98FA-B5EEBD6BBA94@gentoo.org>

On 2022-11-06, Sam James wrote:
>
>
>> On 6 Nov 2022, at 18:17, Fangrui Song via Libc-alpha <libc-alpha@sourceware.org> wrote:
>>
>> lld does not dump a linker script with --verbose (it does not use a
>> linker script driven design and lots of linker processing is not
>> serializable as a linker script anyway).  With the default
>> --with-default-link=no build, $@T is empty and makes `test -s $@T` fail.
>>
>> Just dump the linker script with -fuse-ld=bfd.  lld since 15
>> (https://reviews.llvm.org/D124656) supports custom RELRO sections in the
>> GNU ld dumped linker script.
>> ---
>
>What if bfd isn't installed?

Then --with-default-link=yes has to be used:)

  reply	other threads:[~2022-11-06 23:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 18:17 Fangrui Song
2022-11-06 21:21 ` Sam James
2022-11-06 23:06   ` Fangrui Song [this message]
2022-11-06 23:12     ` Sam James
2022-11-06 23:15       ` Fangrui Song
2022-11-06 23:15         ` Sam James
2022-11-06 23:21       ` Fangrui Song
2022-11-07  8:31 ` Florian Weimer
2022-11-08  0:06   ` Sam James
2022-11-08  0:22     ` Fangrui Song
2022-11-08  0:29       ` Sam James

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='CAFP8O3+=Fb_cN-de8+JuksVSk1u6ZEaYdDZKBNPfF10hkO_2cQ@mail.gmail.com' \
    --to=maskray@google.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sam@gentoo.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 read-only IMAP folder(s) and NNTP newsgroup(s).