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 [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id B9A46389041E for ; Mon, 26 Apr 2021 18:13:00 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B9A46389041E Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-247-TQ4ywi76M_SSGYvOqW0t8A-1; Mon, 26 Apr 2021 14:12:58 -0400 X-MC-Unique: TQ4ywi76M_SSGYvOqW0t8A-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 32987107ACF4; Mon, 26 Apr 2021 18:12:57 +0000 (UTC) Received: from oldenburg.str.redhat.com (ovpn-113-20.ams2.redhat.com [10.36.113.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2663A1002EE6; Mon, 26 Apr 2021 18:12:55 +0000 (UTC) From: Florian Weimer To: "Dmitry V. Levin" Cc: Andreas Schwab , libc-alpha@sourceware.org Subject: Re: [PATCH 00/17] nptl: Move remaining mutex symbols into libpthread References: <87bla1yrlz.fsf@igel.home> <878s55yqy7.fsf@oldenburg.str.redhat.com> <877dkpyq5d.fsf@igel.home> <87h7jtxbcm.fsf@oldenburg.str.redhat.com> <8735vdyp1y.fsf@igel.home> <87a6plxa5y.fsf@oldenburg.str.redhat.com> <87y2d5x7cj.fsf@igel.home> <87pmyhrkso.fsf@oldenburg.str.redhat.com> <20210426180112.GA10373@altlinux.org> Date: Mon, 26 Apr 2021 20:13:22 +0200 In-Reply-To: <20210426180112.GA10373@altlinux.org> (Dmitry V. Levin's message of "Mon, 26 Apr 2021 21:01:12 +0300") Message-ID: <87fszcsym5.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.84 on 10.5.11.22 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-6.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2021 18:13:01 -0000 * Dmitry V. Levin: > On Mon, Apr 26, 2021 at 07:57:11PM +0200, Florian Weimer via Libc-alpha wrote: >> * Andreas Schwab: >> >> > Does your bison use threads? >> >> No, it's not even linked against libpthread. I didn't know it's an >> option. > > bison itself doesn't use threads, but its gnulib part does nowadays. > Unless configured with --disable-threads, it generates a few weak > references to some libpthread symbols and uses them at runtime. Interesting. Unfortunately I cannot easily get a buildroot with a glibc snapshot right now. I'll see if I can reproduce it on powerpc64le, after creating a suitable environment and rebuilding bison in it. Andreas, do you use some statically linked bootstrap bison? There are some iffy weak declarations in that could cause problems for static builds. Thanks, Florian