From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb <gdb@sources.redhat.com>, binutils <binutils@sources.redhat.com>
Subject: Re: parallel builds failing in bfd
Date: Wed, 28 May 2003 22:06:00 -0000 [thread overview]
Message-ID: <20030528220621.GA24942@nevyn.them.org> (raw)
In-Reply-To: <ro1d6i2pw6r.fsf@jackfruit.Stanford.EDU>
On Wed, May 28, 2003 at 03:01:48PM -0700, David Carlton wrote:
> Every once in a while, when I do a parallel build from the top level,
> I get a failure that stems from bfd.h being built incorrectly. Do
> other people run into this problem? I'm not at all familiar with
> bfd's Makefile.in, so I don't know offhand what might be causing this
> problem.
It's an autoconf 2.13 bug unfortunately. It will be fixed after the
2.5x transition, which is starting to gain a little momentum now.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-28 22:06 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 [this message]
2003-05-28 22:51 ` Nicholas Wourms
2003-05-28 23:59 ` DJ Delorie
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=20030528220621.GA24942@nevyn.them.org \
--to=drow@mvista.com \
--cc=binutils@sources.redhat.com \
--cc=carlton@math.stanford.edu \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).