From: Geoff Keating <geoffk@geoffk.org>
To: mark@codesourcery.com
Cc: dj@redhat.com, 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 14:20:00 -0000 [thread overview]
Message-ID: <200207042120.g64LKT521737@desire.geoffk.org> (raw)
In-Reply-To: <61310000.1025803091@warlock.codesourcery.com> (message from Mark Mitchell on Thu, 04 Jul 2002 10:18:11 -0700)
> Date: Thu, 04 Jul 2002 10:18:11 -0700
> From: Mark Mitchell <mark@codesourcery.com>
> --On Thursday, July 04, 2002 12:36:38 PM -0400 DJ Delorie <dj@redhat.com>
> wrote:
>
> >
> >> 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?
>
> Yes -- but this is exactly the kind of thing that I think we can live
> without.
>
> I know people do this; I know it's convenient.
...
It may be that it's easier to replace this usage with another
convenient way to do things. For instance, GCC is supposed to be
location-independent; perhaps we could ask that people who would use
'make install' to install on multiple machines in different places
instead use the (well-tested and often-used) facilities to install in
an alternative directory, and then use 'tar' or a package management
tool to move the binaries to where they need to go.
It's arguable that really, GCC's makefiles shouldn't be dealing with
many of these things at all (like uninstalling or installing over an
earlier version); it's better to delegate them to a real
package-management system.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>
next prev parent reply other threads:[~2002-07-04 21:20 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
2002-07-04 10:19 ` Mark Mitchell
2002-07-04 14:20 ` Geoff Keating [this message]
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=200207042120.g64LKT521737@desire.geoffk.org \
--to=geoffk@geoffk.org \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=geoffk@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