Date: Thu, 14 Nov 2002 22:48:36 +0900 From: NAKAJI Hiroyuki <nakaji@tutrp.tut.ac.jp> To: freebsd-stable@freebsd.org Subject: Re: __stdiooutp Message-ID: <87heekw9cb.fsf@boggy.acest.tutrp.tut.ac.jp> In-Reply-To: <20021114171030.A67189@iclub.nsu.ru> (Max Khon's message of "Thu, 14 Nov 2002 17:10:30 %2B0600") References: <20021114171030.A67189@iclub.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
I have same problem. >>>>> In <20021114171030.A67189@iclub.nsu.ru> >>>>> 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. After SA about bind, I updated my 4.7-STABLE. And got a message Starting innd. /usr/libexec/ld-elf.so.1: /usr/lib/libperl.so.3: Undefined symbol "__stdoutp" > Is this an expected breakage? I had to rebuild libperl with "LDADD+= -lc". But there must be another solution. -- NAKAJI Hiroyuki 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?87heekw9cb.fsf>