From owner-freebsd-ports@FreeBSD.ORG Mon Oct 29 08:47:46 2007 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 15D3616A41A; Mon, 29 Oct 2007 08:47:46 +0000 (UTC) Date: Mon, 29 Oct 2007 08:47:45 +0000 From: Alexey Dokuchaev To: "Carlos A. M. dos Santos" Message-ID: <20071029084745.GB18289@FreeBSD.org> References: <20071027155509.GA34300@ravenloft.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Ports List Subject: Re: Proposition: make x11/nvidia-driver independent of misc/compat5x X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 08:47:46 -0000 On Sat, Oct 27, 2007 at 10:53:30PM -0200, Carlos A. M. dos Santos wrote: > On 10/27/07, Carlos A. M. dos Santos wrote: > > On 10/27/07, Alex Kozlov wrote: > > > On Sat, Oct 27, 2007 at 11:33:46AM -0200, Carlos A. M. dos Santos wrote: > > > > Hello, > > > > > > > > Using the patch below it is possible to make x11/nvidia-driver > > > > independent of misc/compat5x, by means of some library mapping. I did > > > > this successfuly on 6.x but still did not test on 7.x. I would like to > > > > hear some comments before submitting a PR with a change request. What is the problem using compat5x in the first place? > > > I think this is more correct variant: > > > > > > $cat /etc/libmap.conf > > > #nvidia-driver > > > [/usr/local/lib/libGL.so.1] > > > libm.so.3 libm.so.4 > > > > > > [/usr/local/lib/libXvMCNVIDIA.so.1] > > > libc.so.5 libc.so.6 > > > > > > [/usr/local/lib/libXvMCNVIDIA_dynamic.so.1] > > > libc.so.5 libc.so.6 > > > > > > [/usr/local/lib/libnvidia-cfg.so.1] > > > libm.so.3 libm.so.4 > > > > Ah, I forgot that one. Good catch. > > > > > [/usr/local/lib/xorg/modules/libwfb.so] > > > libm.so.3 libm.so.4 > > > librpcsvc.so.2 librpcsvc.so.3 That's potentially unsafe to put next .so version of library when the code expects previous one. It *may* work, but be prepared for all sorts of incompatibilities and ABI breakage. ./danfe