Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 Nov 2000 19:57:53 -0600
From:      "Jeffrey J. Mountin" <jeff-ml@mountin.net>
To:        stable@FreeBSD.ORG
Cc:        Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG>, stable@FreeBSD.ORG
Subject:   Re: libc shlib version (consensus?)
Message-ID:  <4.3.2.20001114192226.00bd9470@207.227.119.2>
In-Reply-To: <20001114145258.A91291@dragon.nuxi.com>
References:  <4.3.2.20001114155102.00c23150@207.227.119.2> <vqc3dgvmpz2.fsf@silvia.hip.berkeley.edu> <31309.974061923@winston.osd.bsdi.com> <200011130413.eAD4DKj41211@vashon.polstra.com> <vqcd7g09vtq.fsf@silvia.hip.berkeley.edu> <200011131605.eADG5H342237@vashon.polstra.com> <20001113095036.C38290@dragon.nuxi.com> <vqc3dgvmpz2.fsf@silvia.hip.berkeley.edu> <20001113152610.C39667@dragon.nuxi.com> <4.3.2.20001114155102.00c23150@207.227.119.2>

next in thread | previous in thread | raw e-mail | index | archive | help
At 02:52 PM 11/14/00 -0800, David O'Brien wrote:
>On Tue, Nov 14, 2000 at 04:03:19PM -0600, Jeffrey J. Mountin wrote:
> > Is the bump going to happen before 4.2 or not?
>
>I don't know.  I'd like to hear Satoshi's response to my last email on
>the topic.  The typical test [in this case] would be does a 4.0R shared
>binary still run fine on a 4.2-R system.  No one has brought this up as
>the case.  And for the example given, I don't know how bumping libc's
>shared version number will solve the problem.

Did some checking and the problem might go back further than first 
assumed.  Looks like it might be just after 4.0R, so the suggestion to 
upgrade might be the easiest path and revisit this post 4.2R.

Wonder if a 4.1R system and the upgrade kit have the same problem?  Ditto 
for 4.1.1R.

Didn't scour the commits, but looked at the PR mentioned and re-read all 
messages.  I'll have to check later, as I keep commits separated for each 
release.  There was a commit on the 12th adding to libc.  That however was 
one month after the PR.

Surprising that someone doesn't know what might have borked things for 
ports.  Satoshi mentioned libxpg4 earlier in the thread.  The commit on the 
12th might either add or fix the problem, otherwise have to look back to 
June on the 4th and 12-14th for libxpg4 stuff.

Hope that helps.


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve



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?4.3.2.20001114192226.00bd9470>