Date: Mon, 17 Feb 1997 17:39:29 +0800 From: Peter Wemm <peter@spinner.DIALix.COM> To: Bruce Evans <bde@zeta.org.au> Cc: obrien@NUXI.com, cvs-all@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-ports@freefall.freebsd.org, pst@shockwave.com Subject: Re: cvs commit: src/contrib/gcc/config/i386 freebsd-elf.h freebsd.h Message-ID: <199702170939.RAA01402@spinner.DIALix.COM> In-Reply-To: Your message of "Mon, 17 Feb 1997 20:13:24 %2B1100." <199702170913.UAA23467@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: > >/etc/make.conf and bsd.port.mk are only used by the port wrapper makefiles. > >/etc/make.conf and bsd.port.mk are totally ignored by 99.99% of vendor > >Makefiles. You can't have bsd.port.mk pass things like 'CFLAGS=... > >-D__FreeBSD__' to all the real makefiles because many will break as they > >build CFLAGS from other definitions, and some don't even use CFLAGS at all. > > /etc/make.conf is actually used if /usr/bin/make is used. Putting flags > in CC instead of in CFLAGS is more likely to work. (Do many ports detect > /usr/bin/gcc and set CC to get it?) This doesn't help for gmake of course. I think this will break for all autoconf ports (quite a lot now it seems) which detect the CC name. Yes, I forgot about sys.mk being always included. BTW, I think we should be installing a specs text file rather than beating up the gcc configuration... It's a much simpler place to deal with things like predefined symbols etc. > Bruce Cheers, -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702170939.RAA01402>