Date: Thu, 2 Nov 2006 12:33:31 -0500 (EST) From: Daniel Eischen <deischen@freebsd.org> To: Maxim Sobolev <sobomax@freebsd.org> Cc: "current@freebsd.org" <current@freebsd.org>, julian@elischer.org Subject: Re: libpthread shared library version number Message-ID: <Pine.GSO.4.64.0611021228350.13428@sea.ntplx.net> In-Reply-To: <454A2A7E.5070703@FreeBSD.org> References: <454936CA.6060308@FreeBSD.org> <20061102115058.GB10961@rambler-co.ru> <Pine.GSO.4.64.0611020824150.12236@sea.ntplx.net> <454A2A7E.5070703@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2 Nov 2006, Maxim Sobolev wrote: > Daniel Eischen wrote: >> No, in -current we force people to recompile everything. Plus >> we have symbol versioning in the libraries most likely to be >> effected. If we bump, we should enable symbol versioning at >> the same time. > > I don't see any reason to wait. Remember, we don't support backward/forward > binary compatibility for binaries compiled for -CURRENT anyway. The only > reason for this bump is to allow binaries compiled for -STABLE to run on > -CURRENT, which is not currently possible in the case when binary uses > pthreads lib. I'm not saying we should wait; I asked for this a few months ago. But, I've been informed that the latest gcc should be imported first because it records dependency information when linking a shared library to other shared libraries (or something like that). I think the entire library version bump should be done in one commit as opposed to just bumping libpthread. -- DE
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0611021228350.13428>