Date: Wed, 20 Dec 2000 13:30:03 -0500 From: "Donald J . Maddox" <dmaddox@sc.rr.com> To: freebsd-current@freebsd.org Cc: Stephen McKay <mckay@thehub.com.au> Subject: Re: Is compatibility for old aout binaries broken? Message-ID: <20001220133003.B7333@cae88-102-101.sc.rr.com> In-Reply-To: <20001220101409.B8849@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Dec 20, 2000 at 10:14:09AM -0800 References: <obrien@freebsd.org> <200012201315.eBKDFtB24592@dungeon.home> <20001220101409.B8849@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 20, 2000 at 10:14:09AM -0800, David O'Brien wrote: > On Wed, Dec 20, 2000 at 11:15:55PM +1000, Stephen McKay wrote: > > Correcting slightly for your slightly off assumption: The X11 libs were > > probably built on a 3.x box. Their problem is that being newer than > > libc.so.2.2 (or was it libc.so.3.0) they use ___error but libc does not > > supply it. My patches to rtld-aout (that first appeared in FreeBSD > > 3.0) supply ___error in this case. This is the only full fix for this > > situation. > > Why is not changing the XFree86-aoutlibs port to offer libs built on > 2.2.x not the right fix? I was under the impression that this was already the case... The libs in the XFree86-aoutlibs port ARE from 2.2.x. My problem was that I was using libs built on 3.x. 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?20001220133003.B7333>