From: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
To: gcc-patches@gcc.gnu.org
Cc: segher@kernel.crashing.org, meissner@linux.ibm.com
Subject: [PATCH] Remove extra lib directory from --with-advance-toolchain
Date: Thu, 03 Oct 2019 17:08:00 -0000 [thread overview]
Message-ID: <20191003170816.4393-1-tuliom@linux.ibm.com> (raw)
Remove the extra -L directory so that user directories specified at
build time have higher preference over the advance toolchain libraries.
2019-10-03 Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
* config.gcc: Remove an extra -L from --with-advance-toolchain.
---
gcc/config.gcc | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/gcc/config.gcc b/gcc/config.gcc
index 481bc9586a7..d52b5cd2d41 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -4782,14 +4782,12 @@ case "${target}" in
echo "#undef LINK_OS_EXTRA_SPEC32"
echo "#define LINK_OS_EXTRA_SPEC32" \
"\"%(link_os_new_dtags)" \
- "-rpath $prefix/lib -rpath $at/lib" \
- "-L $prefix/lib -L $at/lib\""
+ "-rpath $prefix/lib -rpath $at/lib\""
echo
echo "#undef LINK_OS_EXTRA_SPEC64"
echo "#define LINK_OS_EXTRA_SPEC64" \
"\"%(link_os_new_dtags)" \
- "-rpath $prefix/lib64 -rpath $at/lib64" \
- "-L $prefix/lib64 -L $at/lib64\""
+ "-rpath $prefix/lib64 -rpath $at/lib64\""
echo
echo "#undef LINK_OS_NEW_DTAGS_SPEC"
echo "#define LINK_OS_NEW_DTAGS_SPEC" \
--
2.14.5
next reply other threads:[~2019-10-03 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 17:08 Tulio Magno Quites Machado Filho [this message]
2019-10-03 23:32 ` Michael Meissner
2019-10-04 21:32 ` [PATCHv2] Change the library search path when using --with-advance-toolchain Tulio Magno Quites Machado Filho
2019-10-05 17:21 ` Segher Boessenkool
2019-10-23 21:51 ` Peter Bergner
2019-10-07 20:46 ` Michael Meissner
2019-10-08 15:10 ` Segher Boessenkool
2019-10-04 16:13 ` [PATCH] Remove extra lib directory from --with-advance-toolchain Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191003170816.4393-1-tuliom@linux.ibm.com \
--to=tuliom@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).