public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Steve Ellcey <sje@cup.hp.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	binutils@sourceware.org,	"H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: PATCH: PR binutils/12283: bfd/doc doesn't support parallel build
Date: Wed, 16 Feb 2011 05:09:00 -0000	[thread overview]
Message-ID: <20110216050850.GA26163@gmx.de> (raw)
In-Reply-To: <1297814811.2267.5.camel@hpsje.cup.hp.com>

* Steve Ellcey wrote on Wed, Feb 16, 2011 at 01:06:51AM CET:
> On Fri, 2011-02-04 at 18:51 +0100, Andreas Schwab wrote:
> > Ralf Wildenhues <Ralf.Wildenhues@gmx.de> writes:
> > 
> > > bfd/doc/ChangeLog:
> > > 2011-02-04  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
> > >
> > > 	PR binutils/12283
> > > 	* Makefile.am (stamp-chew): New target.
> > > 	Use throughout as dependency for targets that need chew,
> > > 	instead of depdending on chew.c or on chew directly.
> > > 	* Makefile.in: Regenerate.
> > 
> > I think that means that stamp-chew will need to be distributed, since
> > the distributed *.texi files depend on it.

> I am still interested in this patch as a fix for hppa where the parallel
> builds of chew do not result in identical binaries.

I didn't mean to drop the patch.  I just haven't had the time to test
the changes described below, not being too familiar with how binutils
distribution works yet.

> Would distributing stamp-chew be a problem?

I don't think it is right to do that; other code invokes $(MKDOC) and
for that the chew binary needs to be present in the user build tree.

My idea was to clean stamp-chew when $(MKDOC) was cleaned (i.e., in
MOSTLYCLEANFILES).  It should not be a problem if the texi files rules'
get triggered for the user of a tarball, because the generated files
should be identical.  Even if the rules for the info files get
triggered, they should not be a problem because of the 'missing' script.
But I'd really like to test this well before proposing a new patch.

Thanks,
Ralf

  reply	other threads:[~2011-02-16  5:09 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
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 [this message]
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=20110216050850.GA26163@gmx.de \
    --to=ralf.wildenhues@gmx.de \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=sje@cup.hp.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).