Sorry hit send too soon...
On Thu, 2 Aug 2018 at 14:18, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
>
> On Thu, 2 Aug 2018 at 13:03, Bruno Haible wrote:
>
>> Michael Hudson-Doyle wrote:
>> > > It sounds like you are using $(LIBMULTITHREAD) when you should in fact
>> > > be usin
On Thu, 2 Aug 2018 at 13:03, Bruno Haible wrote:
> Michael Hudson-Doyle wrote:
> > > It sounds like you are using $(LIBMULTITHREAD) when you should in fact
> > > be using $(LTLIBMULTITHREAD). See the module description:
> >
> > This doesn't seem to help. ... I'm just a distro maintainer
> > stabb
Michael Hudson-Doyle wrote:
> > It sounds like you are using $(LIBMULTITHREAD) when you should in fact
> > be using $(LTLIBMULTITHREAD). See the module description:
>
> This doesn't seem to help. ... I'm just a distro maintainer
> stabbing in the dark here!
I may have the light. But I don't know
Thanks for the reply.
On Wed, 1 Aug 2018 at 23:06, Bruno Haible wrote:
> Hi,
>
> Michael Hudson-Doyle wrote:
> > I recently encountered the problem that the patch "threadlib: Fix
> > LIBMULTITHREAD on platforms where --as-needed is enabled" was intended to
> > fix. But unfortunately, the fix doe
Hi,
Michael Hudson-Doyle wrote:
> I recently encountered the problem that the patch "threadlib: Fix
> LIBMULTITHREAD on platforms where --as-needed is enabled" was intended to
> fix. But unfortunately, the fix doesn't actually work because libtool is
> re-ordering the linker commands. In particula
Hi,
I recently encountered the problem that the patch "threadlib: Fix
LIBMULTITHREAD on platforms where --as-needed is enabled" was intended to
fix. But unfortunately, the fix doesn't actually work because libtool is
re-ordering the linker commands. In particular "$stuff -Wl,--push-state
-Wl,--no-
