Re: xterm conflicts with xorg-clients
On Mon, 14 Nov 2005 20:49:30 +, Alex Zbyslaw wrote: I have created a patch based on this link, and now xorg-clients builds just fine. I am attaching a gzipped version of the patch (no idea if attachments will work to the list or not), or you can create one based on the URL (but tabs/spaces will almost certainly mess you up). Unzip it in /usr/ports/x11/xorg-clients/files Or you can do (from memory): cd /usr/ports/x11/xorg-clients make clean extract cd work/xc cp programs/xdriinfo/xdriinfo.c programs/xdriinfo/xdriinfo.c.orig * edit programs/xdriinfo/xdriinfo.c and change the glXGetProcAddress to glXGetProcAddressARB on lines 61/2 (or thereabouts). diff -u programs/xdriinfo/xdriinfo.c.orig programs/xdriinfo/xdriinfo.c ../../files/patch-xdriinfo.c cd ../.. make patch (which should apply cleanly) make (which should finish normally) Then if it all worked you can say portupgrade -w x11/xorg-clients which should install what you have just rebuilt. The patch will survive csvup and would need to be deleted if this issue is ever fixed. Then portupgrade x11/xterm should work fine. --Alex Thanks alot, but it worked to deinstall nvidia-driver first and then update xorg-clients. But I save your patch if the problem reappears with a new update :) -- vh Jeppe W. Larsen Logic is the beginning of wisdom; not the end. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Jeppe Larsen wrote: After running cvsup and portupgrade, I'm having some problems with xterm and some other programs. Portupgrade failed because of the following: === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 And then skipped a bunch of packages. Then i manually deinstalled xterm (that was wrong perhaps?) and now when running portupgrade again it is complaining about some stale dependency to xterm. For example: Stale dependency: amarok-1.3.6 -- xterm-206 -- manually run 'pkgdb -F' to fix, or specify -O to force. Then running pkgdb -F asks me alot of questions regarding this stale dependency and I am not sure what to do with it. Then I read in UPDATING that one must upgrade xorg-clients before xterm, but when i tried portupgrade xorg-clients I got: Stale dependency: xorg-clients-6.8.2 -- xterm-206 Hmm, going in circles. Then i tried with the -F and xorg-clients started to compile, but got an error code 1 with this: cc -o xdriinfo -O2 -fno-strict-aliasing -pipe -march=pentium4 -ansi -pedantic -Wno-system-headers -Dasm=__asm -Wall -Wpointer-arith -Wundef -L/usr/ports/x11/xorg-clients/work/xc/exports/lib xdriinfo.o -lGL -lXext -lX11 -L/usr/X11R6/lib -pthread-Wl,-rpath,/usr/X11R6/lib -Wl,-rpath-link,/usr/ports/x11/xorg-clients/work/xc/exports/lib xdriinfo.o(.text+0x59): In function `main': : undefined reference to `glXGetProcAddress' xdriinfo.o(.text+0x6a): In function `main': : undefined reference to `glXGetProcAddress' *** Error code 1 What to do now? Don't delete any of those dependencies! If you do then you will probably have to re-install those packages to get the dependencies back. I believe upgrading xorg-clients and then xterm should work, if only that damn xorg-clients port would compile! I found this link late last night which might help, but haven't tried it myself yet. http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html If you don't want to do all that then you'll have to get the xterm port back to the state it was before cvsup. Either get it from a backup or try portdowngrade. Deleting xterm port *was* a bad idea, sorry. If you had left it alone then you'd be left with working xorg-client and xterm installed and could either chase the fix above at your leisure or wait for someone to fix it officially. Hope that helps, --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Mon, Nov 14, 2005 at 05:22:08PM +, Alex Zbyslaw wrote: Jeppe Larsen wrote: After running cvsup and portupgrade, I'm having some problems with xterm and some other programs. Portupgrade failed because of the following: === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Don't delete any of those dependencies! If you do then you will probably have to re-install those packages to get the dependencies back. Great. I just had the same problem and I deleted the dependencies ;) This is fun. If I had only waited 10 minutes... I hope I didn't break anything beyond repair. Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Check /usr/ports/UPDATING. There should be a fairly recent entry discussing how to deal with this. Actually it is the first listing in /usr/ports/UPDATING 20051113: AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients AUTHOR: [EMAIL PROTECTED] Xterm no longer installs with '-static' prefix. Users should upgrade XFree86-clients to 4.5.0_1 or xorg-clients to 6.8.2_1 or newer before attempting upgrade of xterm to 206_1 or newer. Previous versions remove xterm on deinstall so CONFLICTS have been set accordingly. Eric * Alex Zbyslaw [EMAIL PROTECTED] [051114 12:22]: Date: Mon, 14 Nov 2005 17:22:08 + From: Alex Zbyslaw [EMAIL PROTECTED] To: Jeppe Larsen [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: xterm conflicts with xorg-clients Jeppe Larsen wrote: After running cvsup and portupgrade, I'm having some problems with xterm and some other programs. Portupgrade failed because of the following: === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 And then skipped a bunch of packages. Then i manually deinstalled xterm (that was wrong perhaps?) and now when running portupgrade again it is complaining about some stale dependency to xterm. For example: Stale dependency: amarok-1.3.6 -- xterm-206 -- manually run 'pkgdb -F' to fix, or specify -O to force. Then running pkgdb -F asks me alot of questions regarding this stale dependency and I am not sure what to do with it. Then I read in UPDATING that one must upgrade xorg-clients before xterm, but when i tried portupgrade xorg-clients I got: Stale dependency: xorg-clients-6.8.2 -- xterm-206 Hmm, going in circles. Then i tried with the -F and xorg-clients started to compile, but got an error code 1 with this: cc -o xdriinfo -O2 -fno-strict-aliasing -pipe -march=pentium4 -ansi -pedantic -Wno-system-headers -Dasm=__asm -Wall -Wpointer-arith -Wundef -L/usr/ports/x11/xorg-clients/work/xc/exports/lib xdriinfo.o -lGL -lXext -lX11 -L/usr/X11R6/lib -pthread-Wl,-rpath,/usr/X11R6/lib -Wl,-rpath-link,/usr/ports/x11/xorg-clients/work/xc/exports/lib xdriinfo.o(.text+0x59): In function `main': : undefined reference to `glXGetProcAddress' xdriinfo.o(.text+0x6a): In function `main': : undefined reference to `glXGetProcAddress' *** Error code 1 What to do now? Don't delete any of those dependencies! If you do then you will probably have to re-install those packages to get the dependencies back. I believe upgrading xorg-clients and then xterm should work, if only that damn xorg-clients port would compile! I found this link late last night which might help, but haven't tried it myself yet. http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html If you don't want to do all that then you'll have to get the xterm port back to the state it was before cvsup. Either get it from a backup or try portdowngrade. Deleting xterm port *was* a bad idea, sorry. If you had left it alone then you'd be left with working xorg-client and xterm installed and could either chase the fix above at your leisure or wait for someone to fix it officially. Hope that helps, --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- === Eric I. Ekong[EMAIL PROTECTED] FreeBSD - The Power to Serve http://www.freebsd.org K Desktop Environment on FreeBSD http://freebsd.kde.org === Laws of Serendipity: (1) In order to discover anything, you must be looking for something. (2) If you wish to make an improved product, you must already be engaged in making an inferior one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Mon, 14 Nov 2005 17:22:08 +, Alex Zbyslaw wrote: Don't delete any of those dependencies! If you do then you will probably have to re-install those packages to get the dependencies back. I believe upgrading xorg-clients and then xterm should work, if only that damn xorg-clients port would compile! I found this link late last night which might help, but haven't tried it myself yet. http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html If you don't want to do all that then you'll have to get the xterm port back to the state it was before cvsup. Either get it from a backup or try portdowngrade. Deleting xterm port *was* a bad idea, sorry. If you had left it alone then you'd be left with working xorg-client and xterm installed and could either chase the fix above at your leisure or wait for someone to fix it officially. Hope that helps, --Alex With portdowngrade i managed to install 206 again, so that might be settled. It seems that the problem with xorg-client is another matter, but this error in the link is from january, and the upgrade to 6.8.2_1 is from yesterday?? -- vh Jeppe W. Larsen Logic is the beginning of wisdom; not the end. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Mike Hernandez wrote: On Mon, Nov 14, 2005 at 05:22:08PM +, Alex Zbyslaw wrote: Jeppe Larsen wrote: After running cvsup and portupgrade, I'm having some problems with xterm and some other programs. Portupgrade failed because of the following: === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Don't delete any of those dependencies! If you do then you will probably have to re-install those packages to get the dependencies back. Great. I just had the same problem and I deleted the dependencies ;) This is fun. If I had only waited 10 minutes... I hope I didn't break anything beyond repair. I don't think so. Keep track of which ports you deleted the dependencies from, then when you have the whole xorg-clients/xterm mess sorted out, just force a re-install of those packages and the right dependencies will come back. Time consuming, but not rocket science ;-) I had to do something like that when interrupting gnome_upgrade early seems to bugger everything a treat, but I got everything back OK (I think!). --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Mon, Nov 14, 2005 at 05:59:40PM +, Alex Zbyslaw wrote: I don't think so. Keep track of which ports you deleted the dependencies from, then when you have the whole xorg-clients/xterm mess sorted out, just force a re-install of those packages and the right dependencies will come back. Time consuming, but not rocket science ;-) I had to do something like that when interrupting gnome_upgrade early seems to bugger everything a treat, but I got everything back OK (I think!). Great ;) I'm still working on my first year with freebsd so this a great learning experience. Without getting too far OT, is there a quick explanation as to why xterm is a separate port? Does it take up so much space that it would bloat a standard Xorg/Xfree install? Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Jeppe Larsen wrote: On Mon, 14 Nov 2005 17:22:08 +, Alex Zbyslaw wrote: I believe upgrading xorg-clients and then xterm should work, if only that damn xorg-clients port would compile! I found this link late last night which might help, but haven't tried it myself yet. http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html With portdowngrade i managed to install 206 again, so that might be settled. It seems that the problem with xorg-client is another matter, but this error in the link is from january, and the upgrade to 6.8.2_1 is from yesterday?? As I said, I just did a quick trawl of google late yesterday (like 2am) and haven't followed up. I don't *know* that it's relevant but it looks like the same error to me. It's not unknown for errors which have been fixed to come crawling back out of the woodwork, so maybe it was fixed once and just came back. That's something the port maintainers would have to speak to, though! I actually have no idea that the problem didn't exist since Jan, since I think I installed nvidia-driver after xorg-clients, so wouldn't have seen the problem. Glad the portdowngrade worked for you. I would just leave those two ports alone for a while until you either see something on this list, or see them being updated through cvsup (or check the ports changes page on the freebsd web site every now and again). Or just try upgrading xorg-clients again in a week. If it doesn't fail, then upgrade xterm. If it does fail, it doesn't matter and try again a week later! --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Eric Ekong wrote: Check /usr/ports/UPDATING. There should be a fairly recent entry discussing how to deal with this. Actually it is the first listing in /usr/ports/UPDATING 20051113: AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients AUTHOR: [EMAIL PROTECTED] Xterm no longer installs with '-static' prefix. Users should upgrade XFree86-clients to 4.5.0_1 or xorg-clients to 6.8.2_1 or newer before attempting upgrade of xterm to 206_1 or newer. Previous versions remove xterm on deinstall so CONFLICTS have been set accordingly. This does *not* explain what to do when the xorg-clients build *fails* when nvidia-driver is installed, nor how to recover if you do something like delete the xterm port. This entry explains why upgrading xterm before xorg-clients will fail, but not why upgrading xorg-clients fails. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On 2005-11-14 13:07, Mike Hernandez [EMAIL PROTECTED] wrote: On Mon, Nov 14, 2005 at 05:59:40PM +, Alex Zbyslaw wrote: I don't think so. Keep track of which ports you deleted the dependencies from, then when you have the whole xorg-clients/xterm mess sorted out, just force a re-install of those packages and the right dependencies will come back. Time consuming, but not rocket science ;-) I had to do something like that when interrupting gnome_upgrade early seems to bugger everything a treat, but I got everything back OK (I think!). Great ;) I'm still working on my first year with freebsd so this a great learning experience. Without getting too far OT, is there a quick explanation as to why xterm is a separate port? Does it take up so much space that it would bloat a standard Xorg/Xfree install? New releases of xterm are made far more often than full X11 releases, so it makes more sense I guess. Every time a new version of xterm is out, you don't really need to download rebuild monster-tarballs with all the X11 sources. A simple portupgrade invocation takes care of updating just xterm: # portupgrade -vuN xterm That's probably why it's a separate port. - Giorgos PS: Please, ignore the automatically forced 'footer' below. It's automatically added by the Exchange server I'm behind of and has no relation whatsoever to non-work email I post. - This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, do not forward this email to any other person, delete this e-mail and destroy all copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Monday 14 November 2005 09:02, Jeppe Larsen wrote: After running cvsup and portupgrade, I'm having some problems with xterm and some other programs. Portupgrade failed because of the following: === xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 And then skipped a bunch of packages. Then i manually deinstalled xterm (that was wrong perhaps?) and now when running portupgrade again it is complaining about some stale dependency to xterm. For example: Stale dependency: amarok-1.3.6 -- xterm-206 -- manually run 'pkgdb -F' to fix, or specify -O to force. Then running pkgdb -F asks me alot of questions regarding this stale dependency and I am not sure what to do with it. Then I read in UPDATING that one must upgrade xorg-clients before xterm, but when i tried portupgrade xorg-clients I got: Stale dependency: xorg-clients-6.8.2 -- xterm-206 Hmm, going in circles. Then i tried with the -F and xorg-clients started to compile, but got an error code 1 with this: cc -o xdriinfo -O2 -fno-strict-aliasing -pipe -march=pentium4 -ansi -pedantic -Wno-system-headers -Dasm=__asm -Wall -Wpointer-arith -Wundef -L/usr/ports/x11/xorg-clients/work/xc/exports/lib xdriinfo.o -lGL -lXext -lX11 -L/usr/X11R6/lib -pthread-Wl,-rpath,/usr/X11R6/lib -Wl,-rpath-link,/usr/ports/x11/xorg-clients/work/xc/exports/lib xdriinfo.o(.text+0x59): In function `main': : undefined reference to `glXGetProcAddress' xdriinfo.o(.text+0x6a): In function `main': : undefined reference to `glXGetProcAddress' *** Error code 1 What to do now? I tested portmanager on this yesterday, it handled the conflict without a hitch, you may want to give it a try: sysutils/portmanager -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Mon, Nov 14, 2005 at 10:24:45AM -0800, Giorgos Keramidas wrote: New releases of xterm are made far more often than full X11 releases, so it makes more sense I guess. Every time a new version of xterm is out, you don't really need to download rebuild monster-tarballs with all the X11 sources. A simple portupgrade invocation takes care of updating just xterm: # portupgrade -vuN xterm That's probably why it's a separate port. Thanks for the quick and concise reply. It made sense to me to have the xorg-clients and server parts as separate pacakges, but I couldn't figure out why xterm would be alone. Now I have an idea :) Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Monday 14 November 2005 09:48 am, Jeppe Larsen wrote: On Mon, 14 Nov 2005 17:22:08 +, Alex Zbyslaw wrote: Don't delete any of those dependencies! If you do then you will probably have to re-install those packages to get the dependencies back. I believe upgrading xorg-clients and then xterm should work, if only that damn xorg-clients port would compile! I found this link late last night which might help, but haven't tried it myself yet. http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040 .html If you don't want to do all that then you'll have to get the xterm port back to the state it was before cvsup. Either get it from a backup or try portdowngrade. Deleting xterm port *was* a bad idea, sorry. If you had left it alone then you'd be left with working xorg-client and xterm installed and could either chase the fix above at your leisure or wait for someone to fix it officially. Hope that helps, --Alex With portdowngrade i managed to install 206 again, so that might be settled. It seems that the problem with xorg-client is another matter, but this error in the link is from january, and the upgrade to 6.8.2_1 is from yesterday?? I found that if I deleted xorg-clients and then xterm, I could reinstall xterm and then xorg-clients. I did this from a KDE session. After all of this was done, I ran pkgdb -F and it didn't have any problem connecting to xterm-206_1. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Kent Stewart writes: I found that if I deleted xorg-clients and then xterm, I could reinstall xterm and then xorg-clients. Huh. I did it the other way around. (Rebuilt xorg, then xterm.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Mon, 14 Nov 2005 14:28:10 -0500, Robert Huff wrote: Kent Stewart writes: I found that if I deleted xorg-clients and then xterm, I could reinstall xterm and then xorg-clients. Huh. I did it the other way around. (Rebuilt xorg, then xterm.) And neither of you got this build error (or something similar)? http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html -- vh Jeppe W. Larsen Logic is the beginning of wisdom; not the end. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Monday 14 November 2005 11:40 am, Jeppe Larsen wrote: On Mon, 14 Nov 2005 14:28:10 -0500, Robert Huff wrote: Kent Stewart writes: I found that if I deleted xorg-clients and then xterm, I could reinstall xterm and then xorg-clients. Huh. I did it the other way around. (Rebuilt xorg, then xterm.) And neither of you got this build error (or something similar)? http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.h tml Never saw it. I don't have anything nvidia provided installed. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Jeppe Larsen writes: I found that if I deleted xorg-clients and then xterm, I could reinstall xterm and then xorg-clients. Huh. I did it the other way around. (Rebuilt xorg, then xterm.) And neither of you got this build error (or something similar)? http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html Couldn't have - I don't have the nvidia driver. (I had problems using portupgrade, went back and read ports/UPDATING, then did things by hand. Took maybe 15 minuted longer than if everything had worked.) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
On Monday 14 November 2005 12:01 pm, Robert Huff wrote: Jeppe Larsen writes: I found that if I deleted xorg-clients and then xterm, I could reinstall xterm and then xorg-clients. Huh. I did it the other way around. (Rebuilt xorg, then xterm.) And neither of you got this build error (or something similar)? http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040 .html Couldn't have - I don't have the nvidia driver. (I had problems using portupgrade, went back and read ports/UPDATING, then did things by hand. Took maybe 15 minuted longer than if everything had worked.) Which is one of the reasons I don't have the nvidia driver installed. If we don't have the source, it won't keep up :). Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xterm conflicts with xorg-clients
Alex Zbyslaw wrote: I believe upgrading xorg-clients and then xterm should work, if only that damn xorg-clients port would compile! I found this link late last night which might help, but haven't tried it myself yet. http://lists.freebsd.org/pipermail/freebsd-i386/2005-January/002040.html I have created a patch based on this link, and now xorg-clients builds just fine. I am attaching a gzipped version of the patch (no idea if attachments will work to the list or not), or you can create one based on the URL (but tabs/spaces will almost certainly mess you up). Unzip it in /usr/ports/x11/xorg-clients/files Or you can do (from memory): cd /usr/ports/x11/xorg-clients make clean extract cd work/xc cp programs/xdriinfo/xdriinfo.c programs/xdriinfo/xdriinfo.c.orig * edit programs/xdriinfo/xdriinfo.c and change the glXGetProcAddress to glXGetProcAddressARB on lines 61/2 (or thereabouts). diff -u programs/xdriinfo/xdriinfo.c.orig programs/xdriinfo/xdriinfo.c ../../files/patch-xdriinfo.c cd ../.. make patch (which should apply cleanly) make (which should finish normally) Then if it all worked you can say portupgrade -w x11/xorg-clients which should install what you have just rebuilt. The patch will survive csvup and would need to be deleted if this issue is ever fixed. Then portupgrade x11/xterm should work fine. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
