public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aron Griffis <agriffis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] using -j1 with distcc?
Date: Wed, 13 Sep 2006 10:34:52 -0400	[thread overview]
Message-ID: <20060913143451.GC25497@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

From bind-9.3.2-r4.ebuild:

    # idea from dev-libs/cyrus-sasl
    if has distcc ${FEATURES}; then
        einfo "You have \"distcc\" enabled"
        einfo "build with MAKEOPTS=\"-j1\""
        jobs="-j1"
    else
        einfo "build with MAKEOPTS=${MAKEOPTS}"
        jobs=""
    fi

    emake ${jobs} || die "failed to compile bind"

I think this is bogus.  If building with distcc reveals a parallel
build issue, then the issue exists with or without distcc, it just
seems to happen less often without it.  We've been down this road
before, maybe people have forgotten?

bind-9.3.2-r4.ebuild failed to build for me on dual ia64.  Building
with -j1 works.

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").

Aron

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-09-13 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 14:34 Aron Griffis [this message]
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
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=20060913143451.GC25497@gentoo.org \
    --to=agriffis@gentoo.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