public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <josmyers@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org,  Jonathan Wakely <jwakely@redhat.com>,
	Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH] libgcc: Don't use weakrefs for glibc 2.34
Date: Mon, 29 Apr 2024 13:44:24 +0000 (UTC)	[thread overview]
Message-ID: <8eaa4872-ee98-c4dd-312-498687ccfffb@redhat.com> (raw)
In-Reply-To: <ZiqfmJDdwgUM54T7@tucnak>

On Thu, 25 Apr 2024, Jakub Jelinek wrote:

> Hi!
> 
> glibc 2.34 and later doesn't have separate libpthread (libpthread.so.0 is a
> dummy shared library with just some symbol versions for compatibility, but
> all the pthread_* APIs are in libc.so.6).

I suspect this has caused link failures in the glibc testsuite for Hurd, 
which still has separate libpthread.

https://sourceware.org/pipermail/libc-testresults/2024q2/012556.html

-- 
Joseph S. Myers
josmyers@redhat.com


  parent reply	other threads:[~2024-04-29 13:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 18:23 Jakub Jelinek
2024-04-25 18:33 ` Richard Biener
2024-04-29 13:44 ` Joseph Myers [this message]
2024-04-29 15:01   ` [PATCH] libgcc: Do use weakrefs for glibc 2.34 on GNU Hurd Jakub Jelinek
2024-04-29 18:32     ` 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=8eaa4872-ee98-c4dd-312-498687ccfffb@redhat.com \
    --to=josmyers@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jwakely@redhat.com \
    --cc=rguenther@suse.de \
    /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).