Date: 13 Nov 2000 14:53:56 -0800 From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) To: John Polstra <jdp@polstra.com> Cc: stable@freebsd.org Subject: Re: libc shlib version Message-ID: <vqc8zqnmqkb.fsf@silvia.hip.berkeley.edu> In-Reply-To: <200011131727.eADHR8c42388@vashon.polstra.com> (John Polstra's message of "Mon, 13 Nov 2000 09:27:08 -0800 (PST)") References: <31309.974061923@winston.osd.bsdi.com> <200011130413.eAD4DKj41211@vashon.polstra.com> <vqcd7g09vtq.fsf@silvia.hip.berkeley.edu> <200011131727.eADHR8c42388@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: John Polstra <jdp@polstra.com> * Thinking about this some more ... does the upgrade kit contain a new * libc? It's hard for me to see how these errors could happen if it * didn't. Yes it does. * If it contains a new libc, that seems like the real problem * to me. It's always risky to use new libs (especially libc) with an * old kernel. New ports and packages didn't work with the old libc because someone moved stuff from libxpg4 to libc without changing the version numbers. Putting it in the upgrade kit was the only way to let 4.0R people use ports-current. Maybe I should have insisted that the libc version change back then. I really wish we could keep the two version numbers from a.out, so I don't have to worry about stuff like this. :< Satoshi 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?vqc8zqnmqkb.fsf>