[Issue 15574] wrong order of linker arguments breaks with as-needed

Jan 17, 2016

Martin Nowak

Jan 18, 2016

Vladimir Panteleev

Nov 18, 2016

John Colvin

Nov 18, 2016

Vladimir Panteleev

https://issues.dlang.org/show_bug.cgi?id=15574 --- Comment #1 from Martin Nowak <code@dawg.eu> --- We should pass any linker arguments in the same order as they were passed to dmd. This requires some refactoring of command line parsing and link part. For pragma(lib) we can only choose between prepending and appending them, both of which has issues. But appending seems like the better choice (so you can add library paths with -L-L) and pragma(lib) shouldn't be used anyhow. --

https://issues.dlang.org/show_bug.cgi?id=15574 John Colvin <john.loughran.colvin@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john.loughran.colvin@gmail. | |com --- Comment #2 from John Colvin <john.loughran.colvin@gmail.com> --- Just want to report that this bug is causing significant friction in a commercial project. It's really important that linker arguments are passed on in the order they were given. --

https://issues.dlang.org/show_bug.cgi?id=15574 John Colvin <john.loughran.colvin@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|wrong order of linker |wrong order of linker |arguments breaks with |arguments |as-needed | --- Comment #3 from John Colvin <john.loughran.colvin@gmail.com> --- This problem isn't actually specific to --as-needed, because the following happens with or without it: Given myLib.a, putting -lmyLib before otherLibThatNeedsMyLib.a on the linker command line will (normally) fail to link, because - working from left to right on the command line - symbols from libraries passed by -l are not kept around unless something has already needed them. --

https://issues.dlang.org/show_bug.cgi?id=15574 Remi Thebault <remi.thebault@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |remi.thebault@gmail.com --- Comment #4 from Remi Thebault <remi.thebault@gmail.com> --- Here is a simple test case to reproduce what is decribed by John: $ git clone https://github.com/rtbo/dmd_link_args_order $ cd dmd_link_args_order $ make app It builds a static lib with C code, a static lib with D code that calls a C function (bindings to the C code) and an D app that uses the D code. $ dmd -ofapp app.d libdsquare.a -L-L. -L-lcsquare issues the following linker command: $ cc app.o -o app -m64 -L. -lcsquare -L/usr/lib -Xlinker --export-dynamic libdsquare.a -Xlinker -Bstatic -lphobos2 -Xlinker -Bdynamic -lpthread -lm -lrt -ldl Note that libdsquare.a is after -lcsquare and causes a link error. An intermediate fix would be to place the *.a files before the linker switches given on the command line. I argue that *.a have much more chances to depend on -l libraries than the opposite. This is what LDC is doing. --

April 17, 2018

[Issue 15574] wrong order of linker arguments

Posted by github-bugzilla@puremagic.com

Permalink

github-bugzilla@puremagic.com

Permalink

https://issues.dlang.org/show_bug.cgi?id=15574

--- Comment #5 from github-bugzilla@puremagic.com ---
Commits pushed to master at https://github.com/dlang/dmd

https://github.com/dlang/dmd/commit/fbaeeaee1cac009d9f7157b7d63ea22dee1d3b0e Fix issue 15574 - wrong order of link arguments

This essentially places *.a arguments before the -l and -L switches in the linker command line.

This allows to link applications that link against a static archive *.a
that depends on -l lib switches.
Such dependency scheme is typical of the following situation:
  - have a D package that contains binding to a C library.
  - this D package is itself built as a static library (libdpackage.a).
  - the C library is built in the same build process as a static library
    (pathtoClib/libclib.a)
  - dmd is invoked in the following way:

  $ dmd ... libdpackage.a -L-LpathtoClib -L-lclib

Currently dmd reorders arguments and places *.a after -l linker switches which causes link errors if the -l points to a static library.

This is especially useful with Dub, which can be configured to probe for the C library, and build it as a static lib if not found system-wide. In both cases, the C library is provided with "libs" json entry.

So this is not about keeping relative order of linker arguments, it is about providing an order of linker arguments that is more sound than the current one.

https://github.com/dlang/dmd/commit/10c8fa536879536b4fa339d8325b7a3ab0990d51 add test for issue 15574

https://github.com/dlang/dmd/commit/6371942b1bf26dc6c65cc7e0668bc82e1974c18d Merge pull request #8172 from rtbo/linker_arg_order

Fix issue 15574 - wrong order of link arguments merged-on-behalf-of: Razvan Nitu <RazvanN7@users.noreply.github.com>

--

https://issues.dlang.org/show_bug.cgi?id=15574 --- Comment #6 from github-bugzilla@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/84b64ff24bd46513aa4622c98a6373002a9e8877 Have issue15574.sh use $(CC) instead of hard coded 'cc'. This fails GNU Guix builds and is in line with other test scripts. Includes a fix for compilation issue with C++ compilers by adding extern "C" definition. https://github.com/dlang/dmd/commit/57944f595e7684ffeffdf615546302b8ddfa530a Merge pull request #8702 from pjotrp/master Have issue15574.sh use $(CC) instead of hard coded 'cc'. merged-on-behalf-of: Petar Kirov <ZombineDev@users.noreply.github.com> --

Forums