From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 366E03858D28 for ; Wed, 9 Feb 2022 15:10:12 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 366E03858D28 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-569-z6LniHNYNLOax4QoAcASbA-1; Wed, 09 Feb 2022 10:10:04 -0500 X-MC-Unique: z6LniHNYNLOax4QoAcASbA-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 513F41B2C981; Wed, 9 Feb 2022 15:10:03 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.193.205]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5E4D38049D; Wed, 9 Feb 2022 15:10:02 +0000 (UTC) From: Florian Weimer To: Christer Solskogen via Libc-help Cc: Christer Solskogen Subject: Re: libpthread.so symlink missing? References: <87ee4c2qi5.fsf@oldenburg.str.redhat.com> Date: Wed, 09 Feb 2022 16:10:00 +0100 In-Reply-To: (Christer Solskogen via Libc-help's message of "Wed, 9 Feb 2022 14:58:09 +0100") Message-ID: <87pmnw13g7.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2022 15:10:13 -0000 * 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