Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 May 2002 08:57:41 +0300
From:      Ruslan Ermilov <ru@FreeBSD.org>
To:        "David O'Brien" <obrien@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src Makefile.inc1 src/gnu/lib Makefile src/gnu/usr.bin Makefile src/gnu/usr.bin/cc Makefile
Message-ID:  <20020516055741.GA26715@sunbay.com>
In-Reply-To: <20020515150513.A14077@dragon.nuxi.com>
References:  <200205151629.g4FGTj062213@freefall.freebsd.org> <20020515150513.A14077@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--XsQoSWH+UP9D9v3l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, May 15, 2002 at 03:05:13PM -0700, David O'Brien wrote:
> On Wed, May 15, 2002 at 09:29:45AM -0700, Ruslan Ermilov wrote:
> > ru          2002/05/15 09:29:45 PDT
> >=20
> >   Modified files:
> >     .                    Makefile.inc1=20
> >     gnu/lib              Makefile=20
> >     gnu/usr.bin          Makefile=20
> >     gnu/usr.bin/cc       Makefile=20
> >   Log:
> >   Make sure to not yet build the GNU C++, but still allow
> >   for the C++ progs to be built with e.g. an old compiler,
> >   CXX=3D/usr/bin/c++, for the time being.
>=20
> Please back this out.  You are removing the ability to use an external
> C++ compiler.
>=20
There's no reason to back this out, it does not break anything listed
below.  Have you actually looked at the diffs?

> Setting CXX=3D/usr/bin/c++ is bad advice -- if it was usable we would not
> be in the situation we are in now.
>=20
The point was to say that it's now possible to use CXX=3D/foo/path/c++,
and ${CXX:T} =3D=3D "c++" effectively prevented this.  I've replaced it
with ${CXX} =3D=3D "c++" (which designates the system compiler, unless
the PATH is specially constructed).

> I envision users to set CXX=3D/usr/local/bin/g++31, as that is the C++
> compiler Ports now uses.  The only gotcha is needing to have gperf
> already installed on a system.  Would you be able to add a test for the
> existance of gperf before trying to build src/gnu/usr.bin/cc/cc1plus?
> It would have to test for the existance of /usr/bin/gperf (for older
> systems that have this from Gcc 2.95 days; and
> ${.OBJDIR}/<somehwere>/gperf for the CXX=3Dg++31 case).
>=20
Makefile.inc1 takes care of building "gperf" in bootstrap-tools, so
in a normal bootstrapping sequence no special hacks are necessary.
gperf(1) is first built as a bootstrap-tool in a host environment.
It's then used to build cross-tools (including cc1plus), and the
latter is then used to build gperf(1) for installworld.


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

--XsQoSWH+UP9D9v3l
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE840pVUkv4P6juNwoRAiArAJ0bi994pNI3bAPh4lL7SBsO3NftqwCdGeP+
PzH2ZDvFebjIFCMAViD3uoo=
=7oel
-----END PGP SIGNATURE-----

--XsQoSWH+UP9D9v3l--

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?20020516055741.GA26715>