From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org
Subject: Re: glibc build failure for Hurd with mainline GCC
Date: Mon, 18 Oct 2021 00:52:59 +0200 [thread overview]
Message-ID: <20211017225259.izhdgam7tfcsbvvj@begin> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2110142111050.4143528@digraph.polyomino.org.uk>
Hello,
Joseph Myers, le jeu. 14 oct. 2021 21:15:59 +0000, a ecrit:
> The build failures in the compilers stage of a build-many-glibcs.py build
> are now down to just a failure for i686-gnu, which I hope the Hurd
> maintainers might look at.
Yep, that was an old hack to pass parameters over. I have now reworked
it, it should be much safer now.
Samuel
prev parent reply other threads:[~2021-10-17 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 21:15 Joseph Myers
2021-10-17 22:52 ` Samuel Thibault [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=20211017225259.izhdgam7tfcsbvvj@begin \
--to=samuel.thibault@ens-lyon.org \
--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).