Date: Sat, 18 Jan 1997 00:05:22 +1100 From: Bruce Evans <bde@zeta.org.au> To: joerg_wunsch@uriah.heep.sax.de, thompson@tgsoft.com Cc: freebsd-bugs@freefall.freebsd.org, jkh@time.cdrom.com Subject: Re: bin/2493: make $DESTDIR work Message-ID: <199701171305.AAA14901@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
> Well, i've only heard one objection, that was: ``Name this thing
> TARGETDIR.'' What about this?
>
>Could do that... There are a few existing occurances of
>-I${DESTDIR}/usr/include, which i am now given to understand are "not
>really correct", and should presumably come to be -I${TARGETDIR}/usr/include?
The existing ones are in bsd.lib.mk, bsd.prog.mk and gdb/Makefile.
This is wrong according to bsd.README and comments in *mk which say that
${DESTDIR} only gives the tree to install in. However, it does sort
of work. After bootstrapping to install all includes and libraries under
${DESTDIR}, you can build everything else using only a few wrong libraries
(-I- and -nostdlib aren't used, so there is a large risk of picking up
the wrong includes or libraries if the bootstrap isn't complete, and gcc
generates absolute pathnames for crt0.o and libgcc.a so those are always
taken from the wrong tree). After installing everything under ${DESTDIR},
you can then change ${DESTDIR} and install a copy under the new ${DESTDIR}
without rebuilding much.
I'd like to rename ${DESTDIR} to ${TARGETDIR} for the first type of use.
This is necessary for putting the bootstrap and final versions under
different trees. ${DESTDIR} should not be wrtitten to at build time
and ${TARGETDIR} should not be written to at install time unless they
are the same.
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701171305.AAA14901>