Date: Wed, 21 Sep 2011 13:54:22 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: which "include" being used? Message-ID: <j5cj9k$8su$1@dough.gmane.org> In-Reply-To: <B8E24F18-E145-40EC-80CC-913784D9AF4B@gmail.com> References: <CAN6yY1tF92Sp2NS=Crr1wn7uvuuOeY%2B_j-eOOFPcMZ2ErxnQ9Q@mail.gmail.com> <1316560232.58213.YahooMailClassic@web120530.mail.ne1.yahoo.com> <CAN6yY1to1tdofcErNecuGw=47WxKC5-XT0n=OrJ=KONJjTrByw@mail.gmail.com> <B8E24F18-E145-40EC-80CC-913784D9AF4B@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 21/09/2011 04:34, Garrett Cooper wrote: > On Sep 20, 2011, at 6:19 PM, Kevin Oberman <kob6558@gmail.com> 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 compiler >> and toolchain which uses the existing system include files. >> >> Later in buildworld, they are re-built using the new toolchain, compiler, >> and header files. >> >> If you lost your system header files, you will need to restore them before >> you can re-build the system. >> Sorry. > > 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. [-- Attachment #2 --] -----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?j5cj9k$8su$1>