Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Jul 2003 09:37:19 -0700
From:      Gordon Tetlow <gordont@gnf.org>
To:        Tim Kientzle <kientzle@acm.org>
Cc:        current@freebsd.org
Subject:   Re: Buildworld fails in 5.1
Message-ID:  <20030721163719.GI12996@roark.gnf.org>
In-Reply-To: <3F1C1695.30409@acm.org>
References:  <20030715100839.F41961@inton.Ninja-assassin.com> <20030716133802.K18278@schnell.net> <20030716181354.GA44980@dan.emsphone.com> <20030717074756.B17029@gamplex.bde.org> <20030717123524.T24327@schnell.net> <20030718154832.K21942@gamplex.bde.org> <20030718095946.H29869@schnell.net> <3F183EF9.7020506@acm.org> <20030721084750.GH12996@roark.gnf.org> <3F1C1695.30409@acm.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--e7MbhXUj+2isZwqc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 21, 2003 at 09:36:37AM -0700, Tim Kientzle wrote:
> Gordon Tetlow wrote:
> >It seems that the $(OUTPUTS) target (which has 3 components) causes
> >this particular error.
> >
> >+.ORDER: $(OUTPUTS)
> > $(OUTPUTS): $(CONF)
> >        MAKEOBJDIRPREFIX=3D${CRUNCHOBJS} crunchgen -q -m $(OUTMK) -c $(O=
UTC)=20
> >        \
> >            $(CONF)
>=20
> Hmmm...  Is that what .ORDER is for?  To work around a
> parallel make that gratuitously rebuilds things?

Right it serializes build dependencies. The problem with crunchgen is
that a single command makes all of the OUTPUTS, so normally make will
spawn off the same command 3 times in parallel (which seems to cause
problems). To get around it, make it so you each of the OUTPUTS is
built in order and what occurs is a single crunchgen invocation that
the sees that the other OUTPUT targets are up-to-date and then
contintues along.

> >After doing that, I run into a problem with clparse.o from the dhclient
> >build. I think I might have a solution for that, but I'm too tired
> >right now to think straight. I'll look at it tomorrow.
>=20
>=20
> A-ha!  I've known that dhclient was a problem, but the
> above gives me an idea.  I wonder if the following helps?

I'll give it a whirl.

-gordon

--e7MbhXUj+2isZwqc
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE/HBa/Ru2t9DV9ZfsRAgXOAKCmcq4/sM48MUuoLF3cJu2xPUQ7DgCdE241
SnWN/aSqVIWnDaw8S/r5nN4=
=84Lg
-----END PGP SIGNATURE-----

--e7MbhXUj+2isZwqc--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030721163719.GI12996>