From: "Tom Browder" <tom.browder@gmail.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Gcc Configure System
Date: Thu, 17 Jan 2008 03:44:00 -0000 [thread overview]
Message-ID: <8bc817ee0801160627j14f26d1dj3629d6ddd501947e@mail.gmail.com> (raw)
In-Reply-To: <8bc817ee0801160431i4bb4fb89xa58b43909f872a7a@mail.gmail.com>
On 1/16/08, Tom Browder <tom.browder@gmail.com> wrote:
> I'm trying to help with a new front end for gcc and have a question
> about the configure system:
>
> I notice that each Makefile generated by configure defines srcdir at
> the top as the directory it is formed in (and then sometimes redefines
> it later).
>
> How, then, should one refer to the absolute root of the source tree
> regardless of the depth of the Makefile?
I should have been a little more specific:
The recommended way to build gcc is to use a clean directory outside
the source tree somthing like this:
mkdir build_dir
cd build_dir
/path/to/gcc_src/configure <options>
I want to know if there is a preferred or defined way to refer to
"/path/to/gcc_src" in build scripts or configure inputs since
"$(srcdir)" seems to be locally defined per Makefile.
Thanks.
-Tom
next prev parent reply other threads:[~2008-01-16 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 1:00 Tom Browder
2008-01-17 3:44 ` Tom Browder [this message]
2008-01-17 4:23 ` Tim Prince
2008-01-17 16:04 ` Ian Lance Taylor
2008-01-17 18:27 ` Tom Browder
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=8bc817ee0801160627j14f26d1dj3629d6ddd501947e@mail.gmail.com \
--to=tom.browder@gmail.com \
--cc=gcc-help@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).