From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] AutoMake and paralle safe makefiles [WAS: using -j1 with distcc?]
Date: Wed, 13 Sep 2006 16:03:43 +0100 [thread overview]
Message-ID: <20060913160343.519ba409@snowdrop.home> (raw)
In-Reply-To: <45081B03.4070607@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Wed, 13 Sep 2006 10:51:47 -0400 Alec Warner <antarus@gentoo.org>
wrote:
| Aron Griffis wrote:
| > From bind-9.3.2-r4.ebuild:
| >
| > Unless somebody can explain how this is valid, I'll go ahead and fix
| > the bind ebuilds (where "fix" means "use -j1 unconditionally since
| > the Makefiles aren't parallel safe").
|
| If I'm using Autotools, aren't they smart enough (given that I
| specify the proper headers, and source files and whatnot) to generate
| parallel safe makefiles? Or is it a shot in the dark as to whether
| it works or not?
You can quite easily screw up Makefile.am and generate unsafe code when
using automake. It doesn't remove the need to know what you're doing.
--
Ciaran McCreesh
Mail : ciaranm at ciaranm.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-13 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-13 14:34 [gentoo-dev] using -j1 with distcc? Aron Griffis
2006-09-13 14:51 ` [gentoo-dev] AutoMake and paralle safe makefiles [WAS: using -j1 with distcc?] Alec Warner
2006-09-13 14:58 ` Diego 'Flameeyes' Pettenò
2006-09-13 15:03 ` Ciaran McCreesh [this message]
2006-09-13 14:52 ` [gentoo-dev] using -j1 with distcc? Brian Harring
2006-09-13 15:26 ` Ferris McCormick
2006-09-13 15:29 ` Aron Griffis
2006-09-13 15:30 ` Aron Griffis
2006-09-13 21:09 ` Konstantin V. Arkhipov
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=20060913160343.519ba409@snowdrop.home \
--to=ciaranm@ciaranm.org \
--cc=gentoo-dev@lists.gentoo.org \
/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