From: "E. Weddington" <ericw@evcohs.com>
To: Ian Lance Taylor <ian@wasabisystems.com>
Cc: 'gcc' <gcc@gcc.gnu.org>
Subject: Re: How to stop GCC from searching for components in --prefix on Windows host?
Date: Wed, 22 Sep 2004 18:37:00 -0000 [thread overview]
Message-ID: <4151B9D0.3080503@evcohs.com> (raw)
In-Reply-To: <m3fz5aqkay.fsf@gossamer.airs.com>
Ian Lance Taylor wrote:
>"E. Weddington" <ericw@evcohs.com> writes:
>
>
>
>>I'm certainly not afraid to patch this distribution to take out the
>>search in --prefix for components as the current searching of PATH (or
>>whatever it does after searching --prefix) works just fine. My
>>questions would be: is this a sane thing to do (considering the
>>problem)? Where would one do this in the code? Is it relatively
>>localized? and... would this situation be considered a bug? should I
>>fill out a bug report?
>>
>>
>
>That is a sane thing to do if there is no path which you are certain
>exists (how about "/"?).
>
That might be a way around it; I build in Cygwin (using --host=mingw32
--build=mingw32) so installing it to that location after building won't
be a problem.
>The code is in gcc/gcc.c; look for calls to
>add_prefix(). It is relatively localized.
>
Thanks for the information.
>I don't personally
>consider this situation to be a bug.
>
>
Would it be reasonable as an enhancement request, though?
Thanks
Eric
next prev parent reply other threads:[~2004-09-22 17:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 16:59 E. Weddington
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 [this message]
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=4151B9D0.3080503@evcohs.com \
--to=ericw@evcohs.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@wasabisystems.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).