From: Mark Mitchell <mark@codesourcery.com>
To: Nathanael Nerode <neroden@doctormoo.dyndns.org>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
"binutils@sources.redhat.com" <binutils@sources.redhat.com>,
"gdb@sources.redhat.com" <gdb@sources.redhat.com>
Subject: Re: configure/make/make install with moving srcdir, builddir...
Date: Thu, 04 Jul 2002 00:19:00 -0000 [thread overview]
Message-ID: <11810000.1025767089@warlock.codesourcery.com> (raw)
In-Reply-To: <20020703231357.GA4054@doctormoo.dyndns.org>
--On Wednesday, July 03, 2002 07:13:57 PM -0400 Nathanael Nerode
<neroden@doctormoo.dyndns.org> wrote:
> OK. I've figured out a relatively efficient way to handle *most* of the
> cases of 'configure', 'make', and 'make install' being done in different
> paths.
>
> There's one case this *can't* handle. The specification of
> ${srcdir} must not change from configure time to make time to
> 'make install' time. In other words, you can't pass a totally different
> srcdir on the 'make' command line and expect it to work.
>
> Is this acceptable, or should I try to get this case?
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.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-07-04 7:19 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 [this message]
2002-07-04 9:36 ` DJ Delorie
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=11810000.1025767089@warlock.codesourcery.com \
--to=mark@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.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