Message-Id: <199509292115.XAA22975@grumble.grondar.za>
To: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Cc: Mark Murray <mark@grondar.za>, "Garrett A. Wollman" <wollman@lcs.mit.edu>,
        "Andrey A. Chernov" <ache@freefall.freebsd.org>,
        CVS-commiters@freefall.freebsd.org, cvs-sbin@freefall.freebsd.org
Subject: Re: cvs commit: src/sbin Makefile 
Date: Fri, 29 Sep 1995 23:15:54 +0200
From: Mark Murray <mark@grondar.za>

> I don't think this is true anymore.  I don't see how having secure
> binaries could prevent you from building non-secure binaries.  It just
> doesn't make any sense.

It didn't make sense. It also didn't work. :-(

> David complained to me last week about make release not working unless
> the libraries are in the chroot tree.  Look at release.2:
> 
> release.2:
>         @cd ${.CURDIR} ; $(MAKE) ckRELEASEDIR
>         cd ${.CURDIR}/../etc && make distrib-dirs DESTDIR=${RD}/trees/bin
>         cd ${.CURDIR}/.. ; make distribute DISTDIR=${RD}/trees
>         cd ${.CURDIR}/../eBones && ( \
>                 make bootstrap ;\

Sure - these are just putting things in the ${DISTDIR} (or should be - with
recent changes it is quite possible that this is broken).

> The make bootstrap will fail (or used too until I did the LDADD fixes to
> eBones) since the libraries aren't *installed* in the bootstrap target
> until after all of eBones is built.  I think it was kprop that fell over
> first.

Ah yes, the LDADD changes. If those are not _correctly_ set to the
appropriate ebones/lib/libfoo/obj/<whatever> then it will fail. At 2.0.5
release time, this was working. I own up to breaking this when I redid
the make files during the Great Repository Copy (tm).

> >I agree though that this make system is ropey as hell...
> 
> Yup.

:-)

--
Mark Murray
46 Harvey Rd, Claremont, Cape Town 7700, South Africa
+27 21 61-3768 GMT+0200
Finger mark@grumble.grondar.za for PGP key