This is the mail archive of the
mailing list for the binutils project.
Re: configure/make/make install with moving srcdir, builddir...
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Geoff Keating <geoffk at redhat dot com>
- Cc: "dj at redhat dot com" <dj at redhat dot com>, "neroden at doctormoo dot dyndns dot org" <neroden at doctormoo dot dyndns dot org>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, "binutils at sources dot redhat dot com" <binutils at sources dot redhat dot com>, "gdb at sources dot redhat dot com" <gdb at sources dot redhat dot com>
- Date: Fri, 05 Jul 2002 09:40:16 -0700
- Subject: Re: configure/make/make install with moving srcdir, builddir...
- References: <email@example.com><200207042120.g64LKT521737@desire.geoffk.org>
--On Thursday, July 04, 2002 02:20:29 PM -0700 Geoff Keating
Date: Thu, 04 Jul 2002 10:18:11 -0700
From: Mark Mitchell <firstname.lastname@example.org>
--On Thursday, July 04, 2002 12:36:38 PM -0400 DJ Delorie
>> 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
Yes -- but this is exactly the kind of thing that I think we can live
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.
That's a possibility as well.
In either case, we agree that we don't need this facility in the new
Makefiles before we check them in.
Mark Mitchell email@example.com
CodeSourcery, LLC http://www.codesourcery.com