From: Ian Lance Taylor <iant@google.com>
To: Kyle Girard <kyle@kdmanalytics.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Building Relocatable gcc
Date: Wed, 26 Jan 2011 19:43:00 -0000 [thread overview]
Message-ID: <mcry667v4bt.fsf@google.com> (raw)
In-Reply-To: <1296069846.3050.2187.camel@Tak> (Kyle Girard's message of "Wed, 26 Jan 2011 14:24:06 -0500")
Kyle Girard <kyle@kdmanalytics.com> writes:
>> What do you mean by relocatable?
>>
>> If you use just the --prefix=DIR option, and run "make" and "make
>> install", then you can move the directory DIR wherever you like and
>> everything should continue to work.
>
> By relocatable I mean I guess self contained.. I can use --prefix and
> install the compiler to DIR, yes, but after I rename DIR to DIR2 doesn't
> gcc continue to look for it's headers in DIR?
No. gcc uses relative paths to find its own internal headers.
> If I wanted to zip up the
> gcc in DIR and put it on another machine that doesn't have gcc installed
> on it and doesn't the directory DIR wont it still be looking for headers
> in DIR?
No.
> I'd like to make version of gcc that I can zip up and drop on to a
> machine in a directory of my choice and instantly have a version of gcc
> that I can compile things with. Sort of like the way mingw is done but
> for linux.
That should happen more or less automatically if you follow the simple
procedure I described above.
Ian
next prev parent reply other threads:[~2011-01-26 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 15:27 Kyle Girard
2011-01-26 15:34 ` Ian Lance Taylor
2011-01-26 19:24 ` Kyle Girard
2011-01-26 19:43 ` Ian Lance Taylor [this message]
[not found] <1295993996.3050.2164.camel@Tak>
2011-02-01 23:10 ` Building Relocatable GCC NightStrike
2011-02-02 1:28 ` Bryan Hundven
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=mcry667v4bt.fsf@google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kyle@kdmanalytics.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).