Date: Fri, 15 Nov 2002 10:56:13 -0800 From: steve@Watt.COM (Steve Watt) To: stable@freebsd.org, ler@lerctr.org Subject: Re: __stdiooutp Message-ID: <200211151856.gAFIuDrV022805@wattres.Watt.COM> In-Reply-To: <29010000.1037280536@lerlaptop.lerctr.org> References: <20021114171030.A67189@iclub.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <29010000.1037280536@lerlaptop.lerctr.org> ler@lertcr.org wrote: >--On Thursday, November 14, 2002 17:10:30 +0600 Max Khon ><fjoe@iclub.nsu.ru> wrote: >> Latest changes in stdio have broken compatibility for programs linked with >> both libc.so.3 and some other library which is using stdio and >> which major was not bumped since FreeBSD 3.5 (e.g. libm.so.2 or >> libpam.so.1) -- one will get "Unresolved symbols __stdoutp in libm.so.2" >> error when he tries to run such programs. >> >> Is this an expected breakage? > >Warner MFC'd a new version of libc.so.3 and libc_r.so.3 last weekend in >response to a >PR of mine. > >re-cvsup, and make/installworld. > >LER Didn't help. But setting COMPAT_3X did. But this *isn't* COMPAT_3X, it's COMPAT_4X. One of the machines of mine that displays this has never had a 3.X installed on it. I suppose I can go rebuild all the ports I'm using, but X is painful. -- Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9" Internet: steve @ Watt.COM Whois: SW32 Free time? There's no such thing. It just comes in varying prices... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211151856.gAFIuDrV022805>