Date: Tue, 09 Apr 2002 17:12:34 -0700 From: Peter Wemm <peter@wemm.org> To: obrien@FreeBSD.org Cc: Ruslan Ermilov <ru@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin Makefile Message-ID: <20020410001234.C0BA638CC@overcee.wemm.org> In-Reply-To: <20020409163439.C37507@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"David O'Brien" wrote: > On Tue, Apr 09, 2002 at 11:26:54AM +0300, Ruslan Ermilov wrote: > > > Modified files: > > > gnu/usr.bin Makefile > > > Log: > > > GCC and Gperf do not work on ia64 or sparc64 yet. > > > Also do not try to compile Groff if NO_CXX is set. > > > > > > Revision Changes Path > > > 1.59 +10 -2 src/gnu/usr.bin/Makefile > > > > > This is IMHO bogus. NO_CXX only means that (GNU) c++ shouldn't > > be built, > > This is what we do for PERL. If you have NO_PERL, it perl is not used in > src/secure/lib/libcrypto/Makefile. Why does that not bother you. (I > don't need an answer to that) > > > > it doesn't imply that the host doesn't have another > > working (probably non-GNU) c++ compiler that can build Groff. > > We cannot depend on there being "another working (probably non-GNU) c++ > compiler", thus we WILL NOT. This is still bogus. We need to be able to do a 'make all' at the top of the tree and use external tools. Disconnecting the *building* of gcc etc is one thing, but disconnecting the use of the language is something entirely different. groff, gperf and getconf are perfectly fine on ia64, for example, and you destroyed the build for them as a result of this. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410001234.C0BA638CC>