Date: Sun, 13 Oct 2002 12:43:19 -0700 From: Peter Wemm <peter@wemm.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: Ruslan Ermilov <ru@FreeBSD.ORG>, Kris Kennaway <kris@obsecurity.org>, Hellmuth Michaelis <hm@kts.org>, FreeBSD-current Mailinglist <freebsd-current@FreeBSD.ORG> Subject: Re: HEADS UP: Old port recompiles needed (Re: Unknown symbol "__sF") Message-ID: <20021013194319.7A31D2A88D@canning.wemm.org> In-Reply-To: <3DA9B5B3.5ED38181@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert wrote: > Ruslan Ermilov wrote: > > On Sun, Oct 13, 2002 at 04:27:27AM -0700, Terry Lambert wrote: > > > Kris Kennaway wrote: > > > > If you can't deal with having to recompile things over the -current > > > > development cycle then don't run it. > > > > > > Uh, the issue was the upcoming 5.0 release, which will cause these > > > same problems for people. > > > > As Kris already mentioned in the unquoted part of his original email, > > this does not affect RELENG_4 binaries. > > As I mentioned, it does for 4.6-RELEASE binaries: > > % resize > /usr/libexec/ld-elf.so.1: /usr/lib/libncurses.so.5: \ > Undefined symbol "__stdoutp" > > ...are people going to be upgrading to 5.0-RELEASE from RELENG4, > or are they going to be upgrading from 4.6-RELEASE and 4.7-RELEASE? Add COMPAT4X=true to your make.conf. We added __stdoutp etc to RELENG_4 and included it in the last two releases. -current's COMPAT4X stuff has the updated libc.so.4 with these symbols. If you want to run 4.x binaries, you need COMPAT4X=true so that we can update the 4.x compatability libraries over time. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 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?20021013194319.7A31D2A88D>