From: Jonathan Wakely <jwakely@redhat.com>
To: svante.signell@gmail.com
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: gcc-12: FTBFS on hurd-i386
Date: Fri, 7 Oct 2022 12:41:31 +0100 [thread overview]
Message-ID: <Y0AQa7gMeteud+a7@redhat.com> (raw)
In-Reply-To: <55b2e9b94567fdba6e88e3a35af8773c2ed772e9.camel@gmail.com>
On 06/10/22 18:01 +0200, Svante Signell via Gcc-patches wrote:
>gcc-12-12.2.0-4/5 in sid FTBFS on hurd-i386 due to failing linkage of
>pthread_once (same error for gcc-11, gcc-12, gcc-snapshot):
>/<<PKGBUILDDIR>>/build/i686-gnu/libstdc++-v3/include/i686-gnu/bits/gthr-
>default.h:700: undefined reference to `pthread_once'
>
>Patches have already submitted upstream by Samuel Thibault in August and
>September, see
>https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600469.html
>https://gcc.gnu.org/pipermail/gcc-patches/2022-September/601754.html
>
>Unfortunately upstream is not very responsive.
That's because the patch is for libstdc++ but wasn't CC'd to the
libstdc++ list as required. I've reviewed it now.
prev parent reply other threads:[~2022-10-07 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 16:01 Svante Signell
2022-10-07 11:41 ` Jonathan Wakely [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=Y0AQa7gMeteud+a7@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=svante.signell@gmail.com \
/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).