Marcel Moolenaar scribbled this message on Sep 30:
> Try -DNOTOOLS. I don't know if the -current sources depend specifically
> on -current tools (such as egcs).
well, this may work, but it still doesn't produce a "clean" system to
build with... I don't know the number of times that I've used the
following patch to Makefile.inc1:
+build-env:
+ @echo export PATH=${STRICTTMPPATH}
+ @echo export COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin
+ @echo export GCC_EXEC_PREFIX=${WORLDTMP}/usr/lib/
+ @echo export LD_LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}
+ @echo export LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib
+ @echo export DESTDIR=${WORLDTMP}
+
.include <bsd.subdir.mk>
this allows me to do eval `make build-env`, and suddenly, my build
environment on my 3.0-R box becomes a standard -current world that allows
me to build kernels, programs and other things as if I WAS on a -current
box...
loosing this ability is a big problem for me... I'd even go w/ a simple
option that converts all the signal macros into functions which get
switched depending upon the kernel... and you only get the performance
penalty if you define the option, and it would allow everything to be
backwards compatible...
--
John-Mark Gurney Voice: +1 408 975 9651
Cu Networking
"The soul contains in itself the event that shall presently befall it.
The event is only the actualizing of its thought." -- Ralph Waldo Emerson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
