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: Sat, 05 Feb 2011 00:25:00 -0000 [thread overview]
Message-ID: <1296865501.12233.1357.camel@hpsje.cup.hp.com> (raw)
In-Reply-To: <20110204063423.GC14132@gmx.de>
On Fri, 2011-02-04 at 07:34 +0100, Ralf Wildenhues wrote:
> Still, I don't like the idea of requiring a configure switch in order
> for parallel builds to work; they should just work OOTB.
>
> Maybe we can help things here by going through another indirection,
> that should avoid multiple simultaneous compiles of chew.c.
>
> Does the (little-tested) patch below work for you?
It works fine for me. chew is only built once so there is no problem.
>
> Are you using GNU make by the way, or HP-UX make? I can only warn
> against using the latter:
> http://thread.gmane.org/gmane.comp.sysutils.autoconf.patches/7535/focus=7548
I use GNU make.
Steve Ellcey
sje@cup.hp.com
prev parent reply other threads:[~2011-02-05 0:25 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
2011-02-16 18:36 ` Andreas Schwab
2011-02-05 0:25 ` Steve Ellcey [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=1296865501.12233.1357.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).