From: DJ Delorie <dj@delorie.com>
To: nwourms@myrealbox.com
Cc: gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: parallel builds failing in bfd
Date: Wed, 28 May 2003 23:59:00 -0000 [thread overview]
Message-ID: <200305282359.h4SNx5hN009454@envy.delorie.com> (raw)
In-Reply-To: <3ED53CC0.9040305@myrealbox.com> (message from Nicholas Wourms on Wed, 28 May 2003 18:48:32 -0400)
> BTW, are there any plans to transition to Automake-1.7.X &
> Libtool-1.5.X, now that they have stabilized? It sure would be nice
> to finally have a consolidated, streamlined build without all this
> leftover Cygnus tree building crap. Yes, I dare say to ditch the
> current cruft which is polluting Makefile.in's.
Are you willing to do the work? We got the toplevel files
autoconfiscated only due to a tremendous amount of volunteer time (by
Nate), and any further work is probably also going to have to wait for
someone to volunteers to do it.
next prev parent reply other threads:[~2003-05-28 23:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 22:01 David Carlton
2003-05-28 22:06 ` Daniel Jacobowitz
2003-05-28 22:51 ` Nicholas Wourms
2003-05-28 23:59 ` DJ Delorie [this message]
2003-05-29 20:37 ` amodra
2003-05-30 5:37 ` unsubsribe Gitesh Kulkarni
2003-05-29 13:51 ` parallel builds failing in bfd H. J. Lu
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=200305282359.h4SNx5hN009454@envy.delorie.com \
--to=dj@delorie.com \
--cc=binutils@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=nwourms@myrealbox.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).