public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: John Ericson <mail@johnericson.me>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Optional machine prefix for programs in for -B dirs, matching Clang
Date: Wed, 4 Aug 2021 10:04:03 +0100	[thread overview]
Message-ID: <CAH6eHdTTrLjZAftXQQ-J51_7xL623mqBLb_TWJ8CC3H5ZY02_w@mail.gmail.com> (raw)
In-Reply-To: <8bae6ba2-a4ad-4445-aeb9-e19ece045062@www.fastmail.com>

On Wed, 4 Aug 2021 at 08:41, John Ericson wrote:
>
> On Wed, Aug 4, 2021, at 3:32 AM, Jonathan Wakely via Gcc wrote:
> >
> > Doesn't GCC automatically look for those commands in the --prefix directory
> > that you configure GCC with? Or is that only for native compilers?
> >
>
> It will search only if --with-*=... was not passed, and it will never prefix the query. So yes in practice for cross compilers people do the --with-* and no searching happens, and for native compilers no one bothers and searching does happen. But to be a pedant strictly speaking the behavior is independent of whether the compiler is host == target or not.

I've just checked, and I have a few cross-compilers (for testing
purposes) where I configure binutils and gcc with the same --prefix,
and don't use --with-as or --with-ld, and GCC finds the right
assembler and linker.

So do you need to change anything in GCC? Can't you just not use
--with-as and --with-ld if they are causing problems?

  reply	other threads:[~2021-08-04  9:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04  7:25 John Ericson
2021-08-04  7:32 ` Jonathan Wakely
2021-08-04  7:40   ` John Ericson
2021-08-04  9:04     ` Jonathan Wakely [this message]
2021-08-04 14:48     ` Re: Optional machine prefix for programs in for -B dirs, match ing Clang Michael Matz
2021-08-04 18:04       ` John Ericson
2021-08-05 12:30         ` Michael Matz
2021-08-06  4:13           ` John Ericson
2021-08-04 13:05   ` Optional machine prefix for programs in for -B dirs, matching Clang Paul Koning

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=CAH6eHdTTrLjZAftXQQ-J51_7xL623mqBLb_TWJ8CC3H5ZY02_w@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mail@johnericson.me \
    /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).