Date: Thu, 16 Mar 2000 01:44:50 -0800 From: "David Schwartz" <davids@webmaster.com> To: "Kris Kennaway" <kris@FreeBSD.org> Cc: <stable@freebsd.org> Subject: RE: Upgrading 3.x -> 4.0 STABLE unneccessarily hard Message-ID: <005101bf8f2c$462e5dc0$021d85d1@youwant.to> In-Reply-To: <Pine.BSF.4.21.0003150914570.54359-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Strange. It was a RELENG_3 from just a month or so ago. I wish I'd kept my old libc.a and analyzed it more closely. My recollection was that I did an 'nm' on the libc.a installed and it didn't have 'asprintf' in it and then I did one for the temporary libc.a and it did. So I copied the temporary over the normal libc.a and then it worked. But perhaps I didn't look closely enough. Perhaps a typo in my grep made me thing it didn't have one, but the error was definitely that the symbol 'asprintf' wasn't found. Well, if nobody else reports it, chalk it up to cosmic rays. :) DS > On Tue, 14 Mar 2000, David Schwartz wrote: > > > Upgrading 3.x->4.0 STABLE was made harder than it had to be > because one > > program that is statically linked (objcopy or objdump or something like > > that) was trying to statically link to the system libc.a instead of the > > temporary libc.a. The system libc.a may not have 'asprintf' in > it, bombing > > the make. > > I haven't heard of anyone experiencing this failure mode before. What > value of 'x' do you have? asprintf has been in libc since 1996: 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?005101bf8f2c$462e5dc0$021d85d1>