Date: Tue, 8 Jan 2002 07:50:03 -0800 (PST) From: Sheldon Hearn <sheldonh@starjuice.net> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/33595: libc breaking in -STABLE Message-ID: <200201081550.g08Fo3B16567@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/33595; it has been noted by GNATS. From: Sheldon Hearn <sheldonh@starjuice.net> To: "f.johan.beisser" <jan@caustic.org> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/33595: libc breaking in -STABLE Date: Tue, 08 Jan 2002 17:47:14 +0200 On Tue, 08 Jan 2002 07:36:32 PST, "f.johan.beisser" wrote: > > You _can_ rebuild just libc, but you must use sources synchronized with > > the installed base. In other words, use the same sources used to build > > world. > > so, tracking RELENG_4_4 would work, but RELENG_4 would not? It doesn't matter what you're tracking, so long as, when you do component builds, the component source matches the installed system. Incidentally, this often isn't entirely necessary. You can often get away with component builds from future sources. But since it won't always work (as you've seen for yourself), it's not recommended and can't really be supported. > upgraded source tree that i tend to keep up to date, even if i don't build > from it. that was my mistake. tracking the wrong branch. I'm not sure it had to do so much with tracking the wrong branch as it did with the reasons explained above. > anyhow, now i know, despite several years of working on this stuff. i like > things that keep the OS interesting. Interesting in the Chinese sense of the word. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200201081550.g08Fo3B16567>