From: Segher Boessenkool <segher@kernel.crashing.org>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
Cc: Michael Meissner <meissner@linux.ibm.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCHv2] Change the library search path when using --with-advance-toolchain
Date: Sat, 05 Oct 2019 17:21:00 -0000 [thread overview]
Message-ID: <20191005172059.GS9749@gate.crashing.org> (raw)
In-Reply-To: <20191004213134.8417-1-tuliom@linux.ibm.com>
On Fri, Oct 04, 2019 at 06:31:34PM -0300, Tulio Magno Quites Machado Filho wrote:
> Remove all -L directories from LINK_OS_EXTRA_SPEC32 and
> LINK_OS_EXTRA_SPEC64 so that user directories specified at
> build time have higher preference over the advance toolchain libraries.
>
> Set MD_STARTFILE_PREFIX to $prefix/lib/ and MD_STARTFILE_PREFIX_1 to
> $at/lib/ so that a compiler library has preference over the Advance
> Toolchain libraries.
This is fine, approved for all branches. Thank you! And thanks to Mike
for the testing.
Segher
> 2019-10-04 Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
>
> * config.gcc: Move -L usage from LINK_OS_EXTRA_SPEC32 and
> LINK_OS_EXTRA_SPEC64 to MD_STARTFILE_PREFIX and
> MD_STARTFILE_PREFIX_1 when using --with-advance-toolchain.
next prev parent reply other threads:[~2019-10-05 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 17:08 [PATCH] Remove extra lib directory from --with-advance-toolchain Tulio Magno Quites Machado Filho
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 [this message]
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=20191005172059.GS9749@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=tuliom@linux.ibm.com \
/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).