public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "E. Weddington" <ericw@evcohs.com>
To: gcc <gcc@gcc.gnu.org>
Subject: How to stop GCC from searching for components in --prefix on Windows host?
Date: Wed, 22 Sep 2004 16:59:00 -0000	[thread overview]
Message-ID: <4151A867.5030301@evcohs.com> (raw)

Hello!

I regularly build GCC for the AVR target on a Windows host 
(--host=mingw32) usually with some configured --prefix=X. The binary 
toolset is redistributed to other users who typically don't install it 
in X. There have been some problems where X on the build machine is on a 
particular drive, and on the install machine X is on a drive with 
removable media, then GCC sometimes craps out and doesn't properly 
locate all the components. Is there some way to get GCC to *not* search 
for components in the configured prefix, but preserve its other search 
rules?

In looking through the manual, I found the GCC_EXEC_PREFIX environment 
variable. Though some users have reported that using this doesn't 
completely solve the problem (and personally I'm not totally convinced 
that it doesn't solve the problem). Is it correct that using 
GCC_EXEC_PREFIX will cause GCC to look there first and then continue 
with the rest of the search (--prefix, PATH, etc.)?

Is there something in the manuals that I'm overlooking?

If it requires patching the source, then could someone point out which 
source code module/functions to take a look at?


(Please CC me in your reply as it's difficult for me to reply to digest 
versions of the gcc list that I receive.)

Thanks for your time and help.
Eric

             reply	other threads:[~2004-09-22 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-22 16:59 E. Weddington [this message]
2004-09-22 17:48 ` Dave Korn
2004-09-22 17:56   ` E. Weddington
2004-09-22 18:34     ` Ian Lance Taylor
2004-09-22 18:37       ` E. Weddington
2004-09-22 18:37         ` Ian Lance Taylor
2004-09-22 18:46           ` E. Weddington
2004-09-22 20:46 ` Geoffrey Keating
2004-09-22 21:56   ` Mark Mitchell
2004-09-22 23:58     ` E. Weddington
2004-09-23  1:29       ` Mark Mitchell
2004-09-23 12:14     ` Dave Korn

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=4151A867.5030301@evcohs.com \
    --to=ericw@evcohs.com \
    --cc=gcc@gcc.gnu.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).