http://d.puremagic.com/issues/show_bug.cgi?id=8127
Summary: dmd link library paths not given precedence over gcc
defaults
Product: D
Version: D2
Platform: All
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: DMD
AssignedTo: nob...@puremagic.com
ReportedBy: j...@neggie.net
--- Comment #0 from John Belmonte <j...@neggie.net> 2012-05-20 19:53:57 PDT ---
Given a machine with globally installed D libraries such as phobos2 which
appear in gcc's default library paths, dmd provides no way to supply a library
path with higher precedence. Any -L-L/path/... given to dmd will have lower
precedence. This makes it very difficult to manage local dmd installs, where
it's essential to override any globally installed versions of the phobos2
library. Likewise for any third-party D libraries which one may be developing.
I believe the problem stems from dmd's inconsistent use of the -Xlinker flag.
The -l and -L link options exist in both native gcc and pass-through forms
(latter by way of -Xlinker or -Wl. The dmd link line uses the gcc native form
for -l, but the pass-through form for -L. This pattern appears to give
precedence to gcc's default library paths during library searches.
If link.c is changed to use native gcc options for both -l and -L, the library
paths supplied to -L will be given precedence over gcc default paths.
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
