Date: Thu, 16 May 2002 13:38:48 +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: <20020516103848.GA65503@sunbay.com> In-Reply-To: <20020516014650.A41621@dragon.nuxi.com> References: <200205151629.g4FGTj062213@freefall.freebsd.org> <20020515150513.A14077@dragon.nuxi.com> <20020516055741.GA26715@sunbay.com> <20020516014650.A41621@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--gKMricLos+KVdGMg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, May 16, 2002 at 01:46:50AM -0700, David O'Brien wrote:
> On Thu, May 16, 2002 at 08:57:41AM +0300, Ruslan Ermilov wrote:
> > > > 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.
^^^^^^^^^^^^
> > There's no reason to back this out, it does not break anything listed
> > below. Have you actually looked at the diffs?
>=20
> Yes I did look at the diffs. What C++ compiler do we have that is named=
=20
> "c++" other than the system one? Certainly none of the GCC ports I
>=20
Obviously I just added _more_ variants for the external C++ compiler.
> > The point was to say that it's now possible to use CXX=3D/foo/path/c++,
>=20
> What "c++" command is this you envision?
>=20
It is the string that matched the ${CXX:T} =3D=3D "c++" before, and doesn't
match ${CXX} =3D=3D "c++" now, so you can now use it.
> > Makefile.inc1 takes care of building "gperf" in bootstrap-tools, so
> > in a normal bootstrapping sequence no special hacks are necessary.
>=20
> Gperf is written in C++. If you have no system C++ compiler and CXX is
> set to its stock value; how are you going to build gperf? We experience
> this in the Sparc64 world where we never had a 2.95 system compiler.
>=20
If that's the case, you want to cross-compile the sparc64 world (or only
gperf) using say i386 version of the sparc64 cross-compiler. I fail to
see how the check of whether "gperf" is in the PATH (the check is as
simple as for kldxref(8) in sys/modules/Makefile) helps you to proceed.
"Cross compiling is next step to porting", to quote Terry.
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
--gKMricLos+KVdGMg
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)
iD8DBQE844w4Ukv4P6juNwoRAsXlAJ9xiTvFHs/22pirrlRHVubp8hyHpQCdEvlz
32YeBTjHkU7+iBROgesWwa0=
=R6P4
-----END PGP SIGNATURE-----
--gKMricLos+KVdGMg--
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?20020516103848.GA65503>