Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: (toplevel) Fix dramatic breakage for ordinary crosses (related to program_transform_name)
Date: Sat, 28 Dec 2002 09:56:00 -0000	[thread overview]
Message-ID: <or8yya58x4.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20021228163419.GA10686@nevyn.them.org>

On Dec 28, 2002, Daniel Jacobowitz <drow@mvista.com> wrote:

> I notice that you moved the .NOTPARALLEL down to the configure section. 

Just because otherwise `make NOTPARALLEL=something' would cause make
to try to build something, not all.

> While it is there what do you think of removing the serialization
> dependencies?

Some day, some day...

Really, the only way to avoid them is to introduce some form of
locking, an idea that DJ vehemently rejects.

Unless...  We could perhaps have NOTPARALLEL set by default, which
would take care of avoiding configurations in parallel even without
serialized dependencies, but a configure option to disable NOTPARALLEL
and introduce locking.  DJ, how does this sound for you?

> Also, top level configure no longer accepts --norecursion.

The autoconf spelling is --no-recursion.  Anyway, it no longer
recurses...  Unfortunately, with autoconf, it gets *really* tricky to
introduce options that are not in the autoconf option space (--with or
--enable), so offering --norecursion for backward-compatibility gets
tricky.

> This means that one has to configure from scratch in any existing
> working directory.

./config.status --recheck?


Oh, perhaps you mean with a config.status that pre-dates
autoconfiscation?  Yeah, this would be tricky...  Editing
config.status is your best bet.  Failing that, well...  Running the
top-level configure again is no such big deal, is it? :-)

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


  reply	other threads:[~2002-12-28 17:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28  4:36 Nathanael Nerode
2002-12-28  8:33 ` Alexandre Oliva
2002-12-28  9:51   ` Daniel Jacobowitz
2002-12-28  9:56     ` Alexandre Oliva [this message]
2002-12-28  9:59       ` Daniel Jacobowitz
2002-12-28 10:41         ` Alexandre Oliva
2002-12-28 10:46           ` Dan Kegel
2002-12-28 11:07             ` DJ Delorie
2002-12-28 12:26               ` Daniel Jacobowitz
2002-12-28 10:50           ` Daniel Jacobowitz
2002-12-28 11:01             ` DJ Delorie
2002-12-28 12:57               ` Alexandre Oliva
2002-12-28 13:51                 ` Alexandre Oliva
2002-12-29 18:57                   ` Alexandre Oliva
2002-12-28 14:14                 ` DJ Delorie
2002-12-28 15:22                   ` Alexandre Oliva
2002-12-28 10:54           ` Alexandre Oliva
2002-12-28 10:49       ` DJ Delorie
2002-12-28 11:00 ` DJ Delorie
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06  0:49 Michael Elizabeth Chastain
2002-12-29  0:39 Michael Elizabeth Chastain
2002-12-29  2:48 ` Alexandre Oliva
2002-12-28 13:22 Michael Elizabeth Chastain
2002-12-28 13:44 ` Alexandre Oliva
2003-01-06  0:04 ` Ben Elliston
2002-12-28  1:00 Nathanael Nerode
2002-12-28  1:22 ` Alexandre Oliva
2002-12-28  1:33 ` Alexandre Oliva
2002-12-28  7:47 ` Kazu Hirata

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=or8yya58x4.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=drow@mvista.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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