Date: Mon, 18 Nov 2002 20:57:24 +0100 From: Joerg Wunsch <j@uriah.heep.sax.de> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.ORG Subject: Re: CPUTYPE cr*p (Was: [kris@FreeBSD.org: 5.0-CURRENT build failure of ports you maintain]) Message-ID: <20021118205724.A64225@uriah.heep.sax.de> In-Reply-To: <20021118191126.GB24116@rot13.obsecurity.org>; from kris@obsecurity.org on Mon, Nov 18, 2002 at 11:11:27AM -0800 References: <20021118141458.D50308@uriah.heep.sax.de> <20021118191126.GB24116@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
As Kris Kennaway wrote: > > What am i supposed to do in order to get cross-compilation working > > properly? > > NO_CPU_CFLAGS=yes > > This is documented in make.conf. At least not in my version of make.conf's man page. Just checked, neither in the current version. I (and obviously not only I) wish that'd be the default though. Oh, it would obviate a flaw with the naming choice (the same as with NO_KERNELCLEAN, NO_KERNELDEPEND, NO_MODULES, ...): negative options are evil. You cannot set ?= them in your make.conf, and override the actual value from the command line. But some people seem to be proud about all this these days. I still don't buy <bsd.cpu.mk> is worth all these hassles. If the compiler should now default to say pentium code, why not change the compiler's default but invent such a complicated structure, and leave it to the people who want to pessimize their own code by adding it manually to CFLAGS in make.conf? Guess time to look for a cleaner OS. How's jkhBSD going now? :-) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) 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?20021118205724.A64225>