Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Geoff Keating <geoffk@redhat.com>
Cc: "dj@redhat.com" <dj@redhat.com>,
	"neroden@doctormoo.dyndns.org" <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: Fri, 05 Jul 2002 09:45:00 -0000	[thread overview]
Message-ID: <5200000.1025887215@gandalf.codesourcery.com> (raw)
In-Reply-To: <200207042120.g64LKT521737@desire.geoffk.org>



--On Thursday, July 04, 2002 02:20:29 PM -0700 Geoff Keating 
<geoffk@geoffk.org> wrote:

>> 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.

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.

Thanks,

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com


  reply	other threads:[~2002-07-05 16:45 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
2002-07-05  9:45         ` Mark Mitchell [this message]
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=5200000.1025887215@gandalf.codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=geoffk@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