From: Andreas Schwab <schwab@linux-m68k.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: DJ Delorie <dj@redhat.com>, Helmut Grohne <helmut@subdivi.de>,
<libc-alpha@sourceware.org>
Subject: Re: state of the install-bootstrap-headers patch
Date: Mon, 05 Mar 2018 22:25:00 -0000 [thread overview]
Message-ID: <87d10iyxax.fsf@linux-m68k.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1803052201351.29732@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 5 Mar 2018 22:08:23 +0000")
On Mär 05 2018, Joseph Myers <joseph@codesourcery.com> wrote:
> All those complications are completely unneccessary and have been so for
> several years. That includes most of the configure options you pass to
> glibc's configure script (--enable-kernel=2.6.32 --disable-profile
> --without-cvs --with-elf --without-gd --disable-sanity-checks --with-tls
> --with-__thread should do nothing whatever useful in recent years for any
> supported glibc configuration) and all the *_cv_* config.cache variables
> you set (likewise obsoleted a long time ago - for example,
> libc_cv_forced_unwind and libc_cv_c_cleanup settings were obsoleted by my
> patch <https://sourceware.org/ml/libc-alpha/2012-03/msg00171.html>).
When I bootstrapped openSUSE for RISC-V I didn't need any such
workarounds either.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2018-03-05 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 20:42 Helmut Grohne
2018-03-05 21:55 ` DJ Delorie
2018-03-05 22:08 ` Joseph Myers
2018-03-05 22:23 ` Andreas Schwab
2018-03-05 22:25 ` Andreas Schwab [this message]
2018-03-05 22:31 ` DJ Delorie
2018-03-06 8:01 ` Joseph Myers
2018-03-05 22:00 ` Joseph Myers
2018-03-06 5:49 ` Helmut Grohne
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=87d10iyxax.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=dj@redhat.com \
--cc=helmut@subdivi.de \
--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).