fix Issue 8127 - dmd link library paths not given precedence over gcc defaults #962
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WalterBright
added a commit
that referenced
this pull request
May 24, 2012
fix Issue 8127 - dmd link library paths not given precedence over gcc defaults
WalterBright
added a commit
that referenced
this pull request
May 24, 2012
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently "-l" linkerflags are given directly to gcc, while "-L" linkerflags use the -Xlinker pass-through mechanism. This change gives the latter directly to gcc as well, allowing library search paths provided to dmd to take precedence over gcc's defaults.