public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
* libpthread.so symlink missing?
@ 2022-02-09 10:00 Christer Solskogen
  2022-02-09 12:06 ` Florian Weimer
  0 siblings, 1 reply; 5+ messages in thread
From: Christer Solskogen @ 2022-02-09 10:00 UTC (permalink / raw)
  To: 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?

-- 
chs


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpthread.so symlink missing?
  2022-02-09 10:00 libpthread.so symlink missing? Christer Solskogen
@ 2022-02-09 12:06 ` Florian Weimer
  2022-02-09 13:58   ` Christer Solskogen
  0 siblings, 1 reply; 5+ messages in thread
From: Florian Weimer @ 2022-02-09 12:06 UTC (permalink / raw)
  To: Christer Solskogen via Libc-help; +Cc: Christer Solskogen

* 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,
Florian


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpthread.so symlink missing?
  2022-02-09 12:06 ` Florian Weimer
@ 2022-02-09 13:58   ` Christer Solskogen
  2022-02-09 15:10     ` Florian Weimer
  0 siblings, 1 reply; 5+ messages in thread
From: Christer Solskogen @ 2022-02-09 13:58 UTC (permalink / raw)
  To: 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.

-- 
chs



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpthread.so symlink missing?
  2022-02-09 13:58   ` Christer Solskogen
@ 2022-02-09 15:10     ` Florian Weimer
  2022-02-10  7:18       ` Christer Solskogen
  0 siblings, 1 reply; 5+ messages in thread
From: Florian Weimer @ 2022-02-09 15:10 UTC (permalink / raw)
  To: Christer Solskogen via Libc-help; +Cc: Christer Solskogen

* 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


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: libpthread.so symlink missing?
  2022-02-09 15:10     ` Florian Weimer
@ 2022-02-10  7:18       ` Christer Solskogen
  0 siblings, 0 replies; 5+ messages in thread
From: Christer Solskogen @ 2022-02-10  7:18 UTC (permalink / raw)
  To: libc-help

On 09.02.2022 16:10, Florian Weimer via Libc-help wrote:

> 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.
> 
You are right. The libpthread.a doesn't exist in this environment.

-- 
chs


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2022-02-10  7:18 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-09 10:00 libpthread.so symlink missing? Christer Solskogen
2022-02-09 12:06 ` Florian Weimer
2022-02-09 13:58   ` Christer Solskogen
2022-02-09 15:10     ` Florian Weimer
2022-02-10  7:18       ` Christer Solskogen

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).