Date: Mon, 11 Jan 1999 10:22:33 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: current@FreeBSD.ORG Subject: /usr/obj/elf, /usr/obj/aout, /usr/obj - breaks make all vs make buildworld, and other things. Time to make elf the default ? Message-ID: <199901111822.KAA96566@apollo.backplane.com>
next in thread | raw e-mail | index | archive | help
If I do a 'make buildworld', the object tree is created in /usr/obj/elf
rather then /usr/obj.
If I then want to make the world again, but without cleaning anything,
'make' alone will not work. Instead, 'make -DNOCLEAN -DNOTOOLS' must be
used.
The difference appears to be in /usr/src/Makefile.inc0. It does not set
up MK_ENV for certain backend targets.
#
# A generic rule for the backend targets.
#
${BKTGTS} :
@cd ${.CURDIR}; ${MAKE} ${.TARGET}
Is there any reason why we can't have it setup the MK_ENV ? As in the
below ?
#
# A generic rule for the backend targets.
#
${BKTGTS} :
@cd ${.CURDIR}; ${MK_ENV} ${MAKE} ${.TARGET}
Now, I realize that if you cd somewhere deep into /usr/src and type make,
it will not use the correct obj tree either. So the question is, is it
time to make elf the default ( i.e. /usr/obj ) and just special case
a.out ( i.e. /usr/obj/a.out ) ????
My personal opinion is: yes, ELF should now be the default without any
OBJFORMAT munging. It would be relatively simple to have the top level
make check whether the user's machine is ELF or not, and to only allow
the user to ( at this point ) convert his machine from a.out to elf before
the user is allowed to compile random source.
-Matt
Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet
Communications & God knows what else.
<dillon@backplane.com> (Please include original email in any response)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901111822.KAA96566>