Trouble upgrading ports collection

[Michael C. Shultz]

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