From: Daniel Jacobowitz <drow@mvista.com>
To: gcc@gcc.gnu.org
Cc: Nathanael Nerode <neroden@gcc.gnu.org>, DJ Delorie <dj@redhat.com>
Subject: Serialization dependencies muck up configure-on-demand
Date: Mon, 23 Dec 2002 11:36:00 -0000 [thread overview]
Message-ID: <20021223182335.GA17240@nevyn.them.org> (raw)
The serializiation dependencies are causing all-gdb to have to configure
things like the assembler. Consider --target=alpha-elf. This isn't
supported in gas but the top level doesn't know that (a separate problem,
for another day, and not the real cause of trouble here). The top level
emits serialization dependencies like:
# Serialization dependencies. Host configures don't work well in parallel to
# each other, due to contention over config.cache. Target configures and
# build configures are similar.
mmalloc/Makefile: intl/Makefile
libiberty/Makefile: mmalloc/Makefile
opcodes/Makefile: libiberty/Makefile
bfd/Makefile: opcodes/Makefile
readline/Makefile: bfd/Makefile
tcl/Makefile: readline/Makefile
tk/Makefile: tcl/Makefile
itcl/Makefile: tk/Makefile
tix/Makefile: itcl/Makefile
libgui/Makefile: tix/Makefile
binutils/Makefile: libgui/Makefile
gas/Makefile: binutils/Makefile
ld/Makefile: gas/Makefile
sid/Makefile: ld/Makefile
sim/Makefile: sid/Makefile
gdb/Makefile: sim/Makefile
etc/Makefile: gdb/Makefile
expect/Makefile: etc/Makefile
dejagnu/Makefile: expect/Makefile
utils/Makefile: dejagnu/Makefile
$(TARGET_SUBDIR)/rda/Makefile: $(TARGET_SUBDIR)/libiberty/Makefile
This means that to build GDB in this tree requires configuring gas, and I've
lost all that I hoped to gain from doing the configury in the makefile.
Do we need the serialization dependencies? While we support all sorts of
versions of Make, do we actually support parallel make on anything that
doesn't recognize .NOTPARALLEL?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-12-23 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-23 11:36 Daniel Jacobowitz [this message]
2002-12-23 12:39 ` DJ Delorie
2002-12-23 12:40 ` Daniel Jacobowitz
2002-12-23 13:46 ` DJ Delorie
2002-12-23 14:37 ` Alexandre Oliva
2002-12-23 15:07 ` DJ Delorie
2002-12-26 1:38 ` Alexandre Oliva
2002-12-26 6:53 ` DJ Delorie
2002-12-23 13:25 Nathanael Nerode
2002-12-23 13:36 ` Daniel Jacobowitz
2002-12-24 15:42 ` Paul D. Smith
2002-12-23 13:28 Nathanael Nerode
2002-12-23 13:34 ` Daniel Jacobowitz
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=20021223182335.GA17240@nevyn.them.org \
--to=drow@mvista.com \
--cc=dj@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).