Date: Sat, 2 Nov 2002 21:38:37 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: "Matthew N. Dodd" <winter@jurai.net>, Mark Murray <mark@grondar.org>, freebsd-current@FreeBSD.ORG Subject: Re: __sF Message-ID: <20021103053837.GA31767@troutmask.apl.washington.edu> In-Reply-To: <20021103044257.GC2880@athlon.pn.xcllnt.net> References: <20021102233215.GA30122@troutmask.apl.washington.edu> <20021102183431.V35807-100000@sasami.jurai.net> <20021102235814.GB30122@troutmask.apl.washington.edu> <20021103044257.GC2880@athlon.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 02, 2002 at 08:42:57PM -0800, Marcel Moolenaar wrote: > On Sat, Nov 02, 2002 at 03:58:14PM -0800, Steve Kargl wrote: > > > > > > > > See the new WANT_COMPAT4_STDIO make.conf knob. > > > > > > This won't be acceptable as the vender will likely not be producing a > > > separate 5.0 build (ie the same build needs to run on both.) until 4.x is > > > EOLed. Forcing people to rebuild libc seems a high barrier to entry. > > > > > > > Maybe I misunderstand you. But, a person running FreeBSD 5.x, > > who wants to runs this vendor's 4.x software, will need to > > build their libc with WANT_COMPAT4_STDIO defined if this > > product needs to see __sF. > > No; you're mixing things up. The compat4x stuff we have now allows > you to run 4.x binaries on 5.x. The problem that WANT_COMPAT4_STDIO > addresses is *compiling* 4.x compatible programs on 5.x! A world > of difference. > I just looked through /usr/lib on the 4.7 live ISO. We are missing a bunch of libraries. See another post with the list. -- Steve 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?20021103053837.GA31767>