From: "Tom Browder" <tom.browder@gmail.com>
To: "Ian Lance Taylor" <iant@google.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Gcc Configure System
Date: Thu, 17 Jan 2008 18:27:00 -0000 [thread overview]
Message-ID: <8bc817ee0801161813v2a569788r2155288921c05d13@mail.gmail.com> (raw)
In-Reply-To: <m3y7apmfti.fsf@localhost.localdomain>
On 16 Jan 2008 16:55:05 -0800, Ian Lance Taylor <iant@google.com> wrote:
> "Tom Browder" <tom.browder@gmail.com> writes:
...
> > 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.
>
> Most Makefiles know where they are in the heirarchy, and thus do not
> require any special handling--they use $(srcdir)/.. or whatever.
>
> Where that is not the case, for libraries which are built using
> multilib, we use the make variable top_srcdir. E.g.,
> libstdc++-v3/Makefile.am uses it.
Thanks, Ian, I'll try that.
-Tom
prev parent reply other threads:[~2008-01-17 2:14 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
2008-01-17 4:23 ` Tim Prince
2008-01-17 16:04 ` Ian Lance Taylor
2008-01-17 18:27 ` Tom Browder [this message]
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=8bc817ee0801161813v2a569788r2155288921c05d13@mail.gmail.com \
--to=tom.browder@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.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).