From: DJ Delorie <dj@redhat.com>
To: mark@codesourcery.com
Cc: neroden@doctormoo.dyndns.org, gcc@gcc.gnu.org,
binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: configure/make/make install with moving srcdir, builddir...
Date: Thu, 04 Jul 2002 09:36:00 -0000 [thread overview]
Message-ID: <200207041636.g64GacS06439@greed.delorie.com> (raw)
In-Reply-To: <11810000.1025767089@warlock.codesourcery.com> (message from Mark Mitchell on Thu, 04 Jul 2002 00:18:09 -0700)
> I think that's fine. And if we can really simplify our makefiles that's
> worth more than being able to change the $srcdir around. We can always
> add that later if someone really, really needs it.
What about the case where you do a build on one machine, and do "make
install" on many others with different mount points? Doesn't that
need to know where srcdir is, yet srcdir is a different location for
them?
next prev parent reply other threads:[~2002-07-04 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-03 16:15 Nathanael Nerode
2002-07-04 0:19 ` Mark Mitchell
2002-07-04 9:36 ` DJ Delorie [this message]
2002-07-04 10:19 ` Mark Mitchell
2002-07-04 14:20 ` Geoff Keating
2002-07-05 9:45 ` Mark Mitchell
2002-07-04 16:34 ` DJ Delorie
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=200207041636.g64GacS06439@greed.delorie.com \
--to=dj@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=mark@codesourcery.com \
--cc=neroden@doctormoo.dyndns.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