From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [1/2] RFC: remove doc/configure
Date: Sat, 20 Nov 2010 04:54:00 -0000 [thread overview]
Message-ID: <20101120045359.GM2634@adacore.com> (raw)
In-Reply-To: <m3pqu19gvc.fsf@fleche.redhat.com>
> b/gdb/ChangeLog:
> 2010-11-19 Tom Tromey <tromey@redhat.com>
>
> * Makefile.in (SUBDIRS): Add doc.
> * configure: Rebuild.
> * configure.ac: Don't configure in doc. Create doc/Makefile.
>
> b/gdb/doc/ChangeLog:
> 2010-11-19 Tom Tromey <tromey@redhat.com>
>
> * Makefile.in (Makefile): Run ../config.status.
> (distclean): Update.
> * configure: Remove.
> * configure.ac: Remove.
I like it :).
configure is often seen as a bottleneck in term of the amount of time
taken to perform builds, especially on Windows where fork/exec just takes
forever. But it's also becoming true on Unix machines where large number
of cores allow all the compilations to be parallelized, so the time to
configure becomes a bigger chunck of the wall-clock time. That could
be a possible argument in favor of fragmenting the configury. But in
this case, this is hardly applicable because:
. The gdb/doc/configure script is really minimal
. All the checks it makes have already been done by gdb/configure.
--
Joel
next prev parent reply other threads:[~2010-11-20 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 20:51 Tom Tromey
2010-11-20 4:54 ` Joel Brobecker [this message]
2010-11-23 14:36 ` Tom Tromey
2010-11-23 14:43 ` Tom Tromey
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=20101120045359.GM2634@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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).