Date: Mon, 15 Mar 2004 19:13:33 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: Max Laier <max@love2party.net> Cc: Harald Schmalzbauer <h@schmalzbauer.de> Subject: Re: NO_TOOLCHAIN really working? Message-ID: <20040315171333.GA56514@ip.net.ua> In-Reply-To: <20040315140641.GA67833@router.laiers.local> References: <200403151444.19971.h@schmalzbauer.de> <20040315140641.GA67833@router.laiers.local>
next in thread | previous in thread | raw e-mail | index | archive | help
--huq684BweRXVnRxX
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 15, 2004 at 03:06:41PM +0100, Max Laier wrote:
> On Mon, Mar 15, 2004 at 02:44:14PM +0100, Harald Schmalzbauer wrote:
> > Dear all,
> >=20
> > I'm currently building -current for an embedded system and have the
> > following line in my make.conf:
> > NO_TOOLCHAIN=3Dyes
>=20
> This makes sure that you do not build or install:
> gnu/usr.bin/{cc, binutils}, usr.bin/{c89, c99, gprof, lex, xlint, yacc}
> =20
True.
> > Why do I see those lines while make buildworld?
>=20
> This might be from the bootstrap stage? The switch affects the final stage
> only.
>=20
We still need to build the "cross" versions of compiler, binutils,
and other tools in the chain, to be able to build the rest of the
world. We may be building for a different TARGET_ARCH, or just
bootstrapping (need to link with new libraries and headers, etc.)
The standard buildworld builds a toolchain in stage 3 of buildworld,
then builds the world (including toolchain) in stage 4 using the
special version of toolchain built in stage 3. (The toolchain
=66rom stage 3 is special because it uses different default paths
to pick up headers, libraries, etc., as opposed to the standard
version.) NO_TOOLCHAIN instructs buildworld to not build (and
later not install in installworld) the toolchain in stage 4.
> > cc -Os -pipe -DIN_GCC -DHAVE_CONFIG_H=20
> <...>
> > -c /usr/src/contrib/gcc/combine.c
>=20
> > And what is the include tree good for if I don't want to have gcc at al=
l?
>=20
> That depends on the situation, but I don't think it's too much of a probl=
em
> to rm the include tree before writing to your flash.
>=20
We can easily add the NO_INCLUDES knob to bsd.incs.mk. I assume
there still be some headers (that are not installed through the
standard way using <bsd.incs.mk>), but that can and should be
dealt with. Good question! I'll add it to my TODO list for
share/mk/.
Cheers,
--=20
Ruslan Ermilov
FreeBSD committer
ru@FreeBSD.org
--huq684BweRXVnRxX
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAVeQ9Ukv4P6juNwoRAphzAJ4z85c9mzXkf+0XQvPBbeV410kk1QCeLymp
6vDB/MUaBENUZi06ogxtMoY=
=8PVD
-----END PGP SIGNATURE-----
--huq684BweRXVnRxX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040315171333.GA56514>