public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: DJ Delorie <dj@delorie.com>
Cc: dhazeghi@yahoo.com, gcc@gcc.gnu.org, binutils@sources.redhat.com,
	gdb@sources.redhat.com
Subject: Re: srcdir == objdir build issues [SC take note]
Date: Fri, 09 May 2003 18:54:00 -0000	[thread overview]
Message-ID: <20030509185416.GA1824@disaster.jaj.com> (raw)
In-Reply-To: <200305091841.h49IfpsU016607@envy.delorie.com>

On Fri, May 09, 2003 at 02:41:51PM -0400, DJ Delorie wrote:
> 
> Given how much trouble I've had keeping ./configure working, I think
> any new twists will end up with the same fate.  At this point, I'd
> accept your solution if I thought it would help, but I think it would
> end up the same as what we have now - unsupportable.

The difference is that the twists up to this point have been spread
everywhere.  All through the configury, all through the makefiles.

> The problem is getting the regular gcc developers to test setups other
> than the common one.  Either they're going to test them, or they
> aren't.  If they're going to test them, we can continue supporting
> ./configure the "natural" way.  If they're not going to test them,
> let's not fool ourselves into thinking we can support it.

The approach that Mark et al proposed and that I implemented doesn't
require constant tweaking, like the current situation.  It doesn't need
to be constantly tested.

To remind the audience, what we're talking about had some discussion here:

    http://gcc.gnu.org/ml/gcc-patches/2002-04/msg00866.html

and some patching here (note this was before the top-level autoconfiscation):

    http://gcc.gnu.org/ml/gcc-patches/2002-04/msg01001.html


I like the idea of making our configury simply require/assume separate
build dirs, but there's no need to reject an in-srcdir *interface* just
because maintaining a parallel in-srcdir *implementation* has been a PITA.

Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2003-05-09 18:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20EC888E-81F7-11D7-9B47-000393681B36@yahoo.com>
2003-05-09 17:55 ` DJ Delorie
2003-05-09 18:19   ` Phil Edwards
2003-05-09 18:41     ` DJ Delorie
2003-05-09 18:54       ` Phil Edwards [this message]
2003-05-09 22:35         ` Alexandre Oliva
2003-05-09 22:14   ` Neil Booth
2003-05-10  1:12 Benjamin Kosnik
2003-05-10  1:40 ` DJ Delorie
2003-05-10  4:56   ` Ian Lance Taylor
2003-05-10  4:57   ` Alexandre Oliva
2003-05-11  0:43   ` Phil Edwards
2003-05-11  0:46     ` 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=20030509185416.GA1824@disaster.jaj.com \
    --to=phil@jaj.com \
    --cc=binutils@sources.redhat.com \
    --cc=dhazeghi@yahoo.com \
    --cc=dj@delorie.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).