Date: 15 May 1998 01:31:39 -0000 From: "Brian Feldman" <brianfeldman@hotmail.com> To: freebsd-current@FreeBSD.ORG Subject: Re: Undefined symbol "___error" Message-ID: <19980515013139.12975.qmail@m2.findmail.com> In-Reply-To: <19980514032226.30338@hydrogen.nike.efn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, it wasn't as complicated to get my system up to 3.0. Since it stopped after almost making the bootstrap tools, I just edited the Makefile and had it build the bootstrap libs first, then the tools; so effectively, if you change that order (which you shouldn't, but have to in this case) nothing gets broken; I never had to actually `install' the latest libc with error(3) changes to get the world to compile (although I did, and it's a long story about using libc_pic.a, etc. *g* I'll never do _that_ again) - Brian Feldman > John Birrell scribbled this message on May 14: > > Terry Lambert wrote: > > > > > does this mean that ALL third party programs that use curses MUST be > > > > > recompiled?!?!?! > > > > > > > > Recompiled, no. Relinked, yes. > > > > > > Actually, it's a define in a header file, si it's "recompiled". > > > > No, it's "relinked" so that a program will know to use the later libc. > > The problem here is not that the libc major number needs to be bumped, > > but *all* other libraries that use errno.h need a major number bump. > > Bruce pointed this out. > > > > Bruce wants the change backed out. I haven't heard from anyone else. > > I want the change backed ASAP!! I can't do buildworlds with this > change... I was about to make modifications so that we can have a > LD_LIBRARY_PATH additiont so we can make a dir like: > /usr/lib/buildworldrequiredlibsbecauseofchanges that will contain local > system friendly libs along with libs that will let buildworld run to > completiong... > > this will allow people to HAVE to buildworld on a 2.2.1-R box to be > able to... (either that or let my 486dx2/66 machine buildworld, but > I don't want to think about how long THAT takes)... > > > Should I bump the major number of all the shared libraries in the > > FreeBSD tree? Should I back out the change and forget about making future > > objects thread-aware? Should I do nothing? > > you should make the build process past version friendly... even if > someone had a prev -current to lib changes... they couldn't do a > buildworld without first building libc and installing, then starting > the buildworld process all over again... > > of course, this is more of a problem of using the freebsd header files > to build the tools to buildworld... > > libs and headers are a matched set... > > -- > John-Mark Gurney Modem Rev/FAX: +1 541 346 9237 > Cu Networking P.O. Box 5693, 97405 > > Live in Peace, destroy Micro$oft, support free software, run FreeBSD > Don't trust anyone you don't have the source for > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980515013139.12975.qmail>