Date: Thu, 11 Apr 2002 10:12:18 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: "David O'Brien" <obrien@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: <20020411071218.GB27950@sunbay.com> In-Reply-To: <20020410180308.C84993@dragon.nuxi.com> References: <200204082038.g38KcuJ36871@freefall.freebsd.org> <20020409082654.GE73475@sunbay.com> <20020410045830.GB10113@dhcp01.pn.xcllnt.net> <20020410174228.GJ98684@sunbay.com> <20020410180308.C84993@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 10, 2002 at 06:03:08PM -0700, David O'Brien wrote: > 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. > > >=20 > > > 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. > > >=20 > > I was talking about Groff. >=20 > 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=3D 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. >=20 If you want to change the semantics of NO_CXX from recently "don't compile c++ compiler" to "don't compile c++ compiler and c++ programs", you will also have to disable building of lib/libc_r, as it also uses c++, in its uthread/uthread_autoinit.cc. What if the user has a compiler installed from the Ports collection and wants to compile c++ programs using it? Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8tTdSUkv4P6juNwoRAhJYAJ45+AVp5MAMRAmmWJfzcruruyNpfACeMlsF 1neM1pszqhvqw8JQM+k7jFE= =6Blh -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb-- 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?20020411071218.GB27950>