From owner-freebsd-questions@FreeBSD.ORG Fri Dec 2 23:20:36 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCFC516A41F for ; Fri, 2 Dec 2005 23:20:36 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED36D43D53 for ; Fri, 2 Dec 2005 23:20:35 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so227098wri for ; Fri, 02 Dec 2005 15:20:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=rlqFCOYAycuU0Zn5DbYeTV6HoNhuF6jZRa/xKPJFfK7tpQvUrakCtQSK6MC0j9SoL5wDz0+B8YkRgV1RkQORguNw2/x8WLlDG4G+GFE3XXuM/9nTSrOvMi/L0aYMOsk1IG/vzz+WmzAJ6+Qtp/jQgDtJ3KXBqXByf24a5zARWQE= Received: by 10.54.149.7 with SMTP id w7mr1046317wrd; Fri, 02 Dec 2005 15:20:35 -0800 (PST) Received: from ringworm.mechee.com ( [71.102.14.129]) by mx.gmail.com with ESMTP id g3sm2389507wra.2005.12.02.15.20.34; Fri, 02 Dec 2005 15:20:35 -0800 (PST) From: "Michael C. Shultz" To: freebsd-questions@freebsd.org, Daniel Bye Date: Fri, 2 Dec 2005 15:20:30 -0800 User-Agent: KMail/1.8.3 References: <439093D2.3020905@wanadoo.fr> <20051202221718.GA35163@catflap.slightlystrange.org> In-Reply-To: <20051202221718.GA35163@catflap.slightlystrange.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512021520.31635.ringworm01@gmail.com> Cc: Subject: Re: Trouble upgrading ports collection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2005 23:20:36 -0000 On Friday 02 December 2005 14:17, Daniel Bye wrote: > On Fri, Dec 02, 2005 at 07:34:58PM +0100, edward wrote: > > : undefined reference to `glXGetProcAddress' > > > > xdriinfo.o(.text+0x5b): In function `main': > > : undefined reference to `glXGetProcAddress' > > > > *** Error code 1 > > > > Stop in /usr/ports/x11/xorg-clients/work/xc/programs/xdriinfo. > > *** Error code 1 > > > > Stop in /usr/ports/x11/xorg-clients/work/xc/programs. > > *** Error code 1 > > > > Stop in /usr/ports/x11/xorg-clients. > > Hi, > > This has been discussed several times on the X11 list - try searching > the archives at > http://www.freebsd.org/cgi/search.cgi?words=glXGetProcAddress&max=25&sort=s >core&index=recent&source=freebsd-x11 > > I had the very same problem a couple of weeks ago, but can't now for the > life of me remember now I fixed it... > > Using portmanager won't get you through this one - I use it in > preference to portupgrade these days, and still had the same problem. > > HTH > > Dan Thanks for the info, is this really the recommended fix??? Remove nvidia-driver port, then upgrade xorg-clients. After that you can reinstall nvidia-driver. I read the above as xorg-clients conflicts with nvidia-driver, if it was set this way here is what portmanager would do: 1) when upgrading xorg-clients finds conflicting port nvidia-driver installed and removes it unless user chooses otherwise before 5 minute timeout 2) Upgrade xorg-clients Athe this point something would have to have a dependency on nvidia-driver for it to be pulled back in automatically else the user is going to need to install it manaually... Well I can see how this situation is causing problems anyways....... Has this issue been resolved yet? From reading your references it seems like this fixed the problem with xdriinfo.c: http://www.freebsd.org/cgi/query-pr.cgi?pr=76257 State-Changed-From-To: open->closed State-Changed-By: anholt State-Changed-When: Wed Nov 30 01:24:24 GMT 2005 State-Changed-Why: A patch has been committed to fix this. But I saw no other solution to handling the nvidia port. -Mike