public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: Why -static-libgcc? (Or: Do we need a build-time libc.so linker script?)
Date: Tue, 19 Apr 2022 13:57:35 +0200	[thread overview]
Message-ID: <874k2p2sls.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2201110057490.444240@digraph.polyomino.org.uk> (Joseph Myers's message of "Tue, 11 Jan 2022 00:58:16 +0000")

* Joseph Myers:

> On Mon, 10 Jan 2022, Florian Weimer via Libc-alpha wrote:
>
>> Do we really need to support building the test suite against a
>> static-only GCC build?
>
> I don't think that's ever worked properly.

Then I think not using -static-libgcc plus a check that installed
objects do not depend on libgcc_s seems strictly superior than using
-static-libgcc: this way, we ensure that we do not pull in libgcc bits
we do not expect to have in glibc (like the unwinder).

Thanks,
Florian


      reply	other threads:[~2022-04-19 11:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 22:16 Florian Weimer
2021-11-24 23:19 ` Joseph Myers
2022-01-10 13:00   ` Florian Weimer
2022-01-10 13:26     ` Adhemerval Zanella
2022-01-11  0:58     ` Joseph Myers
2022-04-19 11:57       ` Florian Weimer [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=874k2p2sls.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.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).