From: Michael Hudson-Doyle <michael.hudson@canonical.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Matthias Klose <doko@ubuntu.com>,
libc-alpha@sourceware.org, bug-gnulib@gnu.org,
binutils@sourceware.org
Subject: Re: Undefined use of weak symbols in gnulib
Date: Tue, 13 Jul 2021 12:22:00 +1200 [thread overview]
Message-ID: <CAJ8wqtfWg4RDvBadiBBarN-eBHDRC_pSrxQ5HTQbOzNJYCf-uw@mail.gmail.com> (raw)
In-Reply-To: <87lf6b8rwz.fsf@oldenburg.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
On Tue, 13 Jul 2021 at 03:37, Florian Weimer <fweimer@redhat.com> wrote:
> * Matthias Klose:
>
> > On 7/12/21 5:03 PM, Florian Weimer via Binutils wrote:
> >> * Michael Hudson-Doyle:
> >>
> >>> Did this thread ever reach a conclusion? I'm testing a snapshot of
> >>> glibc 2.34 in ubuntu and running into this issue -- bison segfaults on
> >>> startup on ppc64el.
> >
> >> We rebuilt bison and a couple of other packages
> >
> > do you have a list of these packages?
>
> I rebuilt everything that had a weak symbol reference to
> pthread_mutexattr_gettype or thread_exit because those two symbols are
> used for the single-thread optimization in current gnulib. The presence
> of these symbols largely depends on at which point the upstream sources
> you use last imported the relevant modules from gnulib, so it's probably
> best to check each distribution individually. According to my notes,
> for us, that was bison, findutils, nano, and gnulib itself.
>
Thanks for the list and the other reply. It doesn't seem quite so bad if
it's only a few packages and we can fix them by rebuilding before the new
libc lands.
Cheers,
mwh
[-- Attachment #2: Type: text/html, Size: 1634 bytes --]
prev parent reply other threads:[~2021-07-13 0:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 5:53 Undefined use of weak symbols in gnulib Florian Weimer
2021-04-27 6:50 ` Paul Eggert
2021-04-27 6:58 ` Florian Weimer
2021-04-27 7:13 ` Paul Eggert
2021-04-27 7:24 ` Andreas Schwab
2021-04-27 11:06 ` Florian Weimer
2021-04-28 0:09 ` Bruno Haible
2021-04-28 2:10 ` H.J. Lu
2021-04-28 2:13 ` H.J. Lu
2021-05-05 20:31 ` Fangrui Song
2021-04-28 8:35 ` Florian Weimer
2021-04-28 13:15 ` Michael Matz
2021-04-28 7:44 ` Florian Weimer
2021-04-28 14:48 ` Bruno Haible
2021-04-28 17:44 ` Florian Weimer
2021-07-17 14:38 ` Bruno Haible
2021-07-17 14:55 ` Florian Weimer
2021-07-17 16:39 ` Bruno Haible
2021-07-27 20:02 ` Joseph Myers
2021-07-27 20:19 ` Florian Weimer
2021-07-27 23:38 ` Paul Eggert
2021-07-17 16:21 ` Bruno Haible
2021-04-27 23:22 ` Bruno Haible
2021-04-27 23:47 ` Bruno Haible
2021-04-28 7:57 ` Florian Weimer
2021-04-28 14:40 ` Bruno Haible
2021-04-28 17:43 ` Florian Weimer
2021-04-29 15:15 ` Bruno Haible
2021-04-30 9:55 ` Florian Weimer
2021-04-29 6:33 ` Ben Pfaff
2021-05-03 1:44 ` Alan Modra
2021-07-12 10:04 ` Michael Hudson-Doyle
2021-07-12 15:03 ` Florian Weimer
2021-07-12 15:30 ` Matthias Klose
2021-07-12 15:37 ` Florian Weimer
2021-07-13 0:22 ` Michael Hudson-Doyle [this message]
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ8wqtfWg4RDvBadiBBarN-eBHDRC_pSrxQ5HTQbOzNJYCf-uw@mail.gmail.com \
--to=michael.hudson@canonical.com \
--cc=binutils@sourceware.org \
--cc=bug-gnulib@gnu.org \
--cc=doko@ubuntu.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).