From: Steve Ellcey <sje@cup.hp.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: binutils@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: PATCH: PR binutils/12283: bfd/doc doesn't support parallel build
Date: Mon, 31 Jan 2011 18:33:00 -0000 [thread overview]
Message-ID: <1296498781.12233.80.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <20110129094232.GD11288@gmx.de>
On Sat, 2011-01-29 at 10:42 +0100, Ralf Wildenhues wrote:
> * Steve Ellcey wrote on Sat, Jan 29, 2011 at 12:32:15AM CET:
> > This patch is intended to be a secondary fix/workaround for the problem
> > that can happen when building bfd/doc using a parallel make. Ralf
> > Wildenhues has a fix to move-if-changed that should fix the problem for
> > any target where compiling a file multiple times will always result in
> > exactly the same binary, but I have at least one platform where this is
> > not the case: hppa*-*-hpux*. So I would also like to have this fix as a
> > backup to Ralf's patch (which I think should also go in).
>
> Note that with the changed move-if-change from gnulib, then instead of
> your patch, you could just use
> export CMPPROG=cmp --ignore-initial=16'
> make -jN
>
> for a successful build.
>
> Cheers,
> Ralf
I tried that method but it did not work. When I use 'cmp
--ignore-initial=16' on object files (.o's) it works fine, but when I
use it to compare the chew binary I get a difference beyond the first 16
bytes (at byte 111 or 112 depending on the binary).
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2011-01-31 18:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 17:00 H.J. Lu
2010-12-02 18:08 ` Ralf Wildenhues
2010-12-02 18:16 ` H.J. Lu
2010-12-02 18:20 ` Ralf Wildenhues
2010-12-02 18:22 ` Ralf Wildenhues
2010-12-02 18:32 ` Ralf Wildenhues
2010-12-02 18:40 ` H.J. Lu
2010-12-02 19:01 ` Ralf Wildenhues
2010-12-19 14:37 ` Ralf Wildenhues
2010-12-19 18:23 ` H.J. Lu
2011-01-27 23:57 ` Steve Ellcey
2011-01-28 20:15 ` PATCH: import move-if-change from gnulib (was: PATCH: PR binutils/12283: bfd/doc doesn't support parallel build) Ralf Wildenhues
2011-01-28 21:12 ` Steve Ellcey
2011-02-12 15:48 ` Ralf Wildenhues
2011-01-28 23:32 ` PATCH: PR binutils/12283: bfd/doc doesn't support parallel build Steve Ellcey
2011-01-29 9:42 ` Ralf Wildenhues
2011-01-31 18:33 ` Steve Ellcey [this message]
2011-02-04 6:34 ` Ralf Wildenhues
2011-02-04 17:51 ` Andreas Schwab
2011-02-16 0:07 ` Steve Ellcey
2011-02-16 5:09 ` Ralf Wildenhues
2011-02-16 18:36 ` Andreas Schwab
2011-02-05 0:25 ` Steve Ellcey
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=1296498781.12233.80.camel@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.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).