From: Florian Weimer <fweimer@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: --disable-shared support
Date: Fri, 29 Jun 2018 10:13:00 -0000 [thread overview]
Message-ID: <e3b2ad2b-76d6-c96d-bf45-2bad70be5803@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1806262105320.29676@digraph.polyomino.org.uk>
On 06/26/2018 11:07 PM, Joseph Myers wrote:
> On Mon, 25 Jun 2018, Florian Weimer wrote:
>
>> --disable-shared has apparently been broken for a long, long time. Should we
>> remove any vestiges of support for it?
>
> I think we should fix this problem (bug 20845), to facilitate
> --disable-shared being used as a way to run the full testsuite for static
> linking.
Is this the only reason for fixing it?
I wonder if we should link and run all tests statically which can run
statically linked, rather than relying on tests opting in explicitly
(which some do).
Thanks,
Florian
next prev parent reply other threads:[~2018-06-29 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 14:49 Florian Weimer
2018-06-26 21:07 ` Joseph Myers
2018-06-29 10:13 ` Florian Weimer [this message]
2018-06-29 16:57 ` Joseph Myers
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=e3b2ad2b-76d6-c96d-bf45-2bad70be5803@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).