Re: Undefined use of weak symbols in gnulib

2021-07-12 Thread Michael Hudson-Doyle
On Tue, 13 Jul 2021 at 03:37, Florian Weimer 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 --

Re: Undefined use of weak symbols in gnulib

2021-07-12 Thread 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 packag

Re: Undefined use of weak symbols in gnulib

2021-07-12 Thread Florian Weimer
* 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

Re: Undefined use of weak symbols in gnulib

2021-07-12 Thread Florian Weimer
* 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. For us it got resolved with a binutils fix: commit b293661219c36e72acb80502a86b51160bb88cfd Author: Alan Mod

Re: Undefined use of weak symbols in gnulib

2021-07-12 Thread Michael Hudson-Doyle
On Tue, 27 Apr 2021 at 17:53, Florian Weimer wrote: > lib/glthread/lock.h has this: > > | /* The way to test at runtime whether libpthread is present is to test > |whether a function pointer's value, such as &pthread_mutex_init, is > |non-NULL. However, some versions of GCC have a bug th