Date: Mon, 18 Nov 2002 13:52:35 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Dimitry Andric <dim@xs4all.nl> Cc: Kris Kennaway <kris@obsecurity.org>, Andy Sparrow <spadger@best.com>, Mikhail Teterin <mi@corbulon.video-collage.com>, stable@FreeBSD.ORG Subject: Re: A workaround for the missing __stderrp? Message-ID: <20021118215211.GD65573@xor.obsecurity.org> In-Reply-To: <1379924590.20021118222050@xs4all.nl> References: <20021118074805.GA99883@rot13.obsecurity.org> <20021118190443.A115727F@CRWdog.demon.co.uk> <20021118192222.GB24245@rot13.obsecurity.org> <1379924590.20021118222050@xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, Nov 18, 2002 at 10:20:50PM +0100, Dimitry Andric wrote: > KK> If it links against 3.x libraries (use 'ldd') then it's a 3.x binary :) > > Well, the weird thing here is that the missing "__stderrp" seems to > come from /usr/lib/libm.so.2, which is NOT a compat library (yet?). > For example, when running a certain 3.x executable I get the message: > > /usr/libexec/ld-elf.so.1: /usr/lib/libm.so.2: Undefined symbol "__stderrp" > > indicating that the problem lies in libm.so.2, not in my executable > per se. No, this is the same problem because that "missing" symbol is defined in the new 3.x libc library. Rebuild with COMPAT3X as instructed and it should go away. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE92WC6Wry0BWjoQKURAhvWAJ98r11s5kyCX+bUfyhBEkRZUVvgEQCg5bT5 TzYkyvekyLuqh+ww5hvepBU= =ykQH -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021118215211.GD65573>