public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Christer Solskogen via Libc-help <libc-help@sourceware.org>
Cc: Christer Solskogen <christer.solskogen@gmail.com>
Subject: Re: libpthread.so symlink missing?
Date: Wed, 09 Feb 2022 16:10:00 +0100	[thread overview]
Message-ID: <87pmnw13g7.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <su0h9i$6l6$1@ciao.gmane.io> (Christer Solskogen via Libc-help's message of "Wed, 9 Feb 2022 14:58:09 +0100")

* Christer Solskogen via Libc-help:

> On 09.02.2022 13:06, Florian Weimer via Libc-help wrote:
>> * Christer Solskogen via Libc-help:
>> 
>>> In order for me to get cross-gcc to build I need to create a symlink
>>> from libpthread.so.0 to libpthread.so. Is that a bug in glibc or is
>>> this intended?
>> It is intended.  glibc 2.34 and later only have an empty
>> libpthread.a,
>> to make -lpthread (and -pthread) work.  libpthread.so.0 is only needed
>> for running old applications that still link against it; it is pretty
>> much empty as well (except for symbol version information).

> Thanks for your reply. I'll just create that symlink until a new GCC
> release is out, then.

I don't think your issue is going to go away with a GCC update.  GCC
just uses -lpthread and does not mind if it is libpthread.a or
libpthread.so.  There must be something else in your environment that
causes this.

Thanks,
Florian


  reply	other threads:[~2022-02-09 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09 10:00 Christer Solskogen
2022-02-09 12:06 ` Florian Weimer
2022-02-09 13:58   ` Christer Solskogen
2022-02-09 15:10     ` Florian Weimer [this message]
2022-02-10  7:18       ` Christer Solskogen

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=87pmnw13g7.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=christer.solskogen@gmail.com \
    --cc=libc-help@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).