[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190729172300.GU1506@brightrain.aerifal.cx>
Date: Mon, 29 Jul 2019 13:23:00 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Linking issues
On Mon, Jul 29, 2019 at 04:01:32PM +0200, Ismael Luceno wrote:
> I've started a port of the Source Mage distribution [0] to musl, but
> I'm having issues in cases like this:
>
> app --explicit--> libA --implicit--> libB.
>
> I've an almost identical system with glibc which works fine.
>
> I've opened a bug report for binutils [1], but it's possible that the
> bug is in gcc (in collect2 maybe?).
>
> Maybe someone else ran into this before...
>
>
> [0] https://sourcemage.org/
> [1] https://sourceware.org/bugzilla/show_bug.cgi?id=24815
I don't entirely understand your problem, but if it's that ld fails to
resolve references from app to a symbol that's only defined in libB
when you just passed -lA, this is a known/intentional binutils change
(I would call it a regression -- it broke -lcurses API with ncurses)
from something like a decade or two ago. Unless you want to fight with
it, the solution is just "don't do that". I believe pkgconf and/or
libtool stuff works around this if you're using them. In any case your
problem probably has more to do with versions or configuration of
tooling than with musl.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
