Re: which "include" being used?

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD140F3C1456C0178AC8BC9D0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 21/09/2011 04:34, Garrett Cooper wrote:
> On Sep 20, 2011, at 6:19 PM, Kevin Oberman <[e-mail]> wrote:

>> To build a new system, you have to start with something. You build the=

>> toolcain  and gcc. Those have to be built first with the existing comp=
iler
>> and toolchain which uses the existing system include files.
>>
>> Later in buildworld, they are re-built using the new toolchain, compil=
er,
>> and header files.
>>
>> If you lost your system header files, you will need to restore them be=
fore
>> you can re-build the system.
>> Sorry.
>=20
> I'd unpack a tarball from the most recent release. It's the easiest way=
 to fix things :)..

I second this suggestion - if the system is damaged enough, this is
really the best and most painless way. Because of API & ABI stability in
FreeBSD STABLE branches, there isn't much that can go wrong even if you
repopulate it (temporarily) with another release's sources.



--------------enigD140F3C1456C0178AC8BC9D0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk550HQACgkQldnAQVacBchAvQCg/fGUybJOLyec9UYcj64uXP45
CxwAn0+svw7DTYNWCzqSEmd+0M7mSAsF
=BtP1
-----END PGP SIGNATURE-----

--------------enigD140F3C1456C0178AC8BC9D0--