Date: Sat, 02 Nov 2002 17:44:06 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: sgk@troutmask.apl.washington.edu Cc: winter@jurai.net, mark@grondar.org, freebsd-current@FreeBSD.ORG Subject: Re: __sF Message-ID: <20021102.174406.74907429.imp@bsdimp.com> In-Reply-To: <20021102235814.GB30122@troutmask.apl.washington.edu> References: <20021102233215.GA30122@troutmask.apl.washington.edu> <20021102183431.V35807-100000@sasami.jurai.net> <20021102235814.GB30122@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20021102235814.GB30122@troutmask.apl.washington.edu>
Steve Kargl <sgk@troutmask.apl.washington.edu> writes:
: 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.
All that kludge does is to allow a program that shouldn't be allowed
to link to link. You need to setup to compile 4.x binaries on the 5.x
machine, or you will lose in the long run. __sF is only the first of
many issues, some subtle, that you'll face cross-threading 4.x and 5.x
libraries.
Warner
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?20021102.174406.74907429.imp>