Linking issues

Linking issues

[Ismael Luceno]

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

Re: Linking issues

[Rich Felker]

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