From: "H. J. Lu" <hjl@lucon.org>
To: Nicholas Wourms <nwourms@myrealbox.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb <gdb@sources.redhat.com>,
binutils <binutils@sources.redhat.com>
Subject: Re: parallel builds failing in bfd
Date: Thu, 29 May 2003 13:51:00 -0000 [thread overview]
Message-ID: <20030529065154.A29255@lucon.org> (raw)
In-Reply-To: <3ED53CC0.9040305@myrealbox.com>; from nwourms@myrealbox.com on Wed, May 28, 2003 at 06:48:32PM -0400
On Wed, May 28, 2003 at 06:48:32PM -0400, Nicholas Wourms wrote:
> Daniel Jacobowitz wrote:
> > 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.
> >
>
> 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
FYI, the current binutils/gdb tree doesn't work with
# make install DESTDIR=foo
when shared library is enabled due to the libtool bug. I put a kludge
in my Linux binutils. I hope it gets fixed soon.
H.J.
prev parent reply other threads:[~2003-05-29 13:51 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
2003-05-29 20:37 ` amodra
2003-05-30 5:37 ` unsubsribe Gitesh Kulkarni
2003-05-29 13:51 ` H. J. Lu [this message]
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=20030529065154.A29255@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.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).