public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: phil@jaj.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:41:00 -0000	[thread overview]
Message-ID: <200305091841.h49IfpsU016607@envy.delorie.com> (raw)
In-Reply-To: <20030509181925.GD1188@disaster.jaj.com> (message from Phil Edwards on Fri, 9 May 2003 14:19:25 -0400)


> There's no reason to make it gratuitously fail.  I implemented a
> patch that would solve both problems: configury only has to deal
> with out-srcdir builds, plus the users can do "./configure; make"
> with no surprises.

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 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.  If the
solution is to build in a separate directory, let's just tell the user
that, require it, and get rid of all the cruft that's been added to
support anything else.  Just getting rid of the cruft will help with
maintenance costs too.

At least then the supported setups will be well tested and maintained.

  reply	other threads:[~2003-05-09 18:41 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 [this message]
2003-05-09 18:54       ` Phil Edwards
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=200305091841.h49IfpsU016607@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=binutils@sources.redhat.com \
    --cc=dhazeghi@yahoo.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=phil@jaj.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).