Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Jan 2011 10:25:44 -0500
From:      Alexander Kabaev <kabaev@gmail.com>
To:        Marcel Moolenaar <xcllnt@mac.com>
Cc:        stable@FreeBSD.org, current@FreeBSD.org, uqs@FreeBSD.org
Subject:   Re: RFC vgrind in base (and buildworld)
Message-ID:  <20110121102544.1bc9222c@kan.dnsalias.net>
In-Reply-To: <CE03E002-9A32-49AC-8C31-1568FCD127E4@mac.com>
References:  <20110120201740.GE24444@acme.spoerlein.net> <20110120153103.50a86ad3@kan.dnsalias.net> <CE03E002-9A32-49AC-8C31-1568FCD127E4@mac.com>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/6=2jSqnCuMBVi/lEapRzMbC
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, 20 Jan 2011 17:11:13 -0800
Marcel Moolenaar <xcllnt@mac.com> wrote:

>=20
> On Jan 20, 2011, at 12:31 PM, Alexander Kabaev wrote:
>=20
> > On Thu, 20 Jan 2011 21:17:40 +0100
> > Ulrich Sp=F6rlein <uqs@FreeBSD.org> wrote:
> >=20
> >> Hello,
> >>=20
> >> Currently our buildworld relies on groff(1) and vgrind(1) being
> >> present in the host system. I have a patch ready that at least
> >> makes sure these are built during bootstrap-tools and completes the
> >> WITHOUT_GROFF flag.
> >>=20
> >> vgrind(1) is only used for two papers under share/doc and we could
> >> easily expand the results and commit them to svn directly,
> >> alleviating the need to run vgrind(1) during buildworld.
> >>=20
> >> OTOH, there are much more useful tools to vgrind(1) for source code
> >> formatting. So do we still have vgrind(1) users out there?
> >>=20
> >> Regards,
> >> Uli
> >=20
> > Why it needs to be in bootsrap tools at all? We have build tools for
> > this exact purpose.
>=20
> Actually no. The buildtools target is there to allow building programs
> that are not installed, but are otehrwise needed to compile a program.
> These are typically little tools that create source files.
>=20
> The bootstrap target is the to deal with compatibility in case we
> can't use the version on the host or we don't want to depend on the
> version on the host.

Then it is cross-tools, or whatever build stage that builds new gcc and
other tools which run on host and are used to generate the final target
binaries. The point being that bootstrap-tools target is greatly abused
in src, with recent addition of llvm libs making it almost pandemic.



--=20
Alexander Kabaev

--Sig_/6=2jSqnCuMBVi/lEapRzMbC
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)

iD8DBQFNOaV9Q6z1jMm+XZYRAvHoAJ41NmHQ1OcmY4QoHVEHwU73R5PSWQCgr5eH
n/Hlo+oFQ6+MrCjRSI0KOJA=
=kW6X
-----END PGP SIGNATURE-----

--Sig_/6=2jSqnCuMBVi/lEapRzMbC--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110121102544.1bc9222c>