Undefined use of weak symbols in gnulib
Michael Hudson-Doyle
michael.hudson@canonical.com
Tue Jul 13 00:22:00 GMT 2021
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
More information about the Binutils
mailing list