Date: Wed, 10 Apr 2002 18:03:08 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: Marcel Moolenaar <marcel@xcllnt.net>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin Makefile Message-ID: <20020410180308.C84993@dragon.nuxi.com> In-Reply-To: <20020410174228.GJ98684@sunbay.com>; from ru@FreeBSD.org on Wed, Apr 10, 2002 at 08:42:28PM %2B0300 References: <200204082038.g38KcuJ36871@freefall.freebsd.org> <20020409082654.GE73475@sunbay.com> <20020410045830.GB10113@dhcp01.pn.xcllnt.net> <20020410174228.GJ98684@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 10, 2002 at 08:42:28PM +0300, Ruslan Ermilov wrote: > > > This is IMHO bogus. NO_CXX only means that (GNU) c++ shouldn't > > > be built, it doesn't imply that the host doesn't have another > > > working (probably non-GNU) c++ compiler that can build Groff. > > > > Unfortunately this is irrelevant, because a buildworld will not > > use it if it exists. The bottomline is that if you don't build > > libstdc++, you cannot build anything that depends on it. Hence, > > making gperf conditional on NO_CXX is correct. > > > I was talking about Groff. So was Marcel. Please come up with a way to not compile Groff and gperf if NO_CXX is set. The assumption there is some external C++ compiler is a rather bogus one. If there is an external C++ compiler the user should be setting CXX= to it. The IA-64 case that Peter yelled at me about is also a very special case. The TYPICAL case is an Alpha or i386 box with NO_CXX set and which we cannot assume there is a C++ compiler available. Otherwise I will simply remove the NO_CXX option as it is broken otherwise. 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?20020410180308.C84993>