From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14466 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Linking issues Date: Mon, 29 Jul 2019 13:23:00 -0400 Message-ID: <20190729172300.GU1506@brightrain.aerifal.cx> References: <20190729140132.GA5137@pirotess.home> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="264840"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-14482-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jul 29 19:23:16 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hs9Mi-0016mk-Fd for gllmg-musl@m.gmane.org; Mon, 29 Jul 2019 19:23:16 +0200 Original-Received: (qmail 30286 invoked by uid 550); 29 Jul 2019 17:23:13 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 30262 invoked from network); 29 Jul 2019 17:23:13 -0000 Content-Disposition: inline In-Reply-To: <20190729140132.GA5137@pirotess.home> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14466 Archived-At: 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