Date: Tue, 14 Nov 2000 15:36:09 -0800 From: Kent Stewart <kstewart@urx.com> To: Drew Tomlinson <drewt@writeme.com> Cc: "'Tim McMillen'" <timcm@umich.edu>, "'FreeBSD Questions (E-mail)'" <freebsd-questions@FreeBSD.ORG> Subject: Re: Errors Installing KDE2 Port Message-ID: <3A11CC69.9F0A3023@urx.com> References: <BA5D0CE1CBB2D411B6AA00A0CC3F02390AF717@ldcmsx01.lc.ca.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
Drew Tomlinson wrote: > > > -----Original Message----- > > From: Kent Stewart [mailto:kstewart@urx.com] > > Sent: Monday, November 13, 2000 4:09 PM > > > > Drew Tomlinson wrote: > > > > > > I know there has been a discussion on this recently but I can't find > > > anything in the archives that pertains to my problem. I'm > > attempting to > > > install KDE2 from the ports tree. I just CVSup'd today, > > November 13 and am > > > still having problems. My steps have been these: > > > > > > 1. cd /usr/ports/x11/kde2 > > > > > > 2. make > > > > > > I have also attempted a "make clean" and then tried again. > > I'm under the > > > impression that this will remove all files related to the > > port. Is this > > > correct? What other options are there and what do they do? > > > > > > Anyway, I'd appreciate any thoughts or ideas. The > > following is the output > > > starting with the last command before the problems start. > > > > What I did to get KDE2 to install was create the README.html for the > > ports. I used this for a check list. Then I deleted KDE1 and all of > > its ports. I had a version of qt-2.x, which caused problems. The > > metaports don't deal with multiple versions of a port. You probably > > have an old Mesa lying around and I did a make clean on each required > > port and then did the make from .../kde2. > > OK, I'm in the process of trying this. There are two sections listed on the > README.html file. One is a list of packages required to build and the other > is a list required to run. I'm going through the list required to run as > it's longer and I want to be sure I don't miss anything. > > My question is that it appears that running "make clean" in each port > direcetory also cleans the related ports. Is this true? If it is, am I > accomplishing anything by doing a "make clean" in ports that have already > been completed because it is tied to another port? And I've also noticed > that a after a "make clean", the program still shows up with a pkg_info. > When this happens, I do a pkg_delete to remove it. So apparently, pkg_* and > make are two separate items. What's the difference between them? The make clean only cleans the port you are cleaning. The big benefit of the make clean is that the next make does a reconfigure and links to the resources it want to use. Frequently there are new versions out there but it doesn't install the updated versions. You have to do that. KDE-2 is touchy and I don't know how far you have to go. I had so many problems that I simply started down the dependancy list and updated all of them. The only one that takes a long time is qt-2.2.1. When you do a make clean you are mostly cleaning out the .../work/ directory for the port. You still have to pkg_delete -f port (usually the older version) before you do the make install to install the port you just built. I found KDE-2 will build all of the ports but the installation is much cleaner if you build the non-KDE dependancies. Most of them probably need to be updated. I don't think there was a one on my systems that didn't have at least a _n after it. When your KDE dependancies are old versions, I find that you are better off if you go through and clean them, make, pkg_delete -f, and make install them before you start the KDE-2 make and make install. When you get through, KDE installs pretty well. Kent > > Thanks again for your help! > > Drew > > > > > I had a working version of KDE2 around 12-18 hours later. > > > > Kent > > > > > > > > Thanks, > > > > > > Drew > > > > > > ---------------------------------------------------------------- > > > cc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -O2 -pipe > > -Wall -fomit-frame-po > > > inte > > > r -ffast-math -fexpensive-optimizations -malign-loops=2 > > -malign-jumps=2 -mal > > > ign- > > > functions=2 -D_REENTRANT -c glut_bitmap.c -fPIC -DPIC -o > > glut_bitmap.lo > > > In file included from glut_bitmap.c:8: > > > glutint.h:19: X11/Xlib.h: No such file or directory > > > glutint.h:20: X11/Xutil.h: No such file or directory > > > In file included from glutint.h:21, > > > from glut_bitmap.c:8: > > > ../include/GL/glx.h:33: X11/Xlib.h: No such file or directory > > > ../include/GL/glx.h:34: X11/Xutil.h: No such file or directory > > > In file included from ../include/GL/glx.h:37, > > > from glutint.h:21, > > > from glut_bitmap.c:8: > > > ../include/GL/xmesa.h:79: X11/Xlib.h: No such file or directory > > > ../include/GL/xmesa.h:80: X11/Xutil.h: No such file or directory > > > In file included from ../include/GL/xmesa.h:81, > > > from ../include/GL/glx.h:37, > > > from glutint.h:21, > > > from glut_bitmap.c:8: > > > ../include/GL/xmesa_x.h:39: syntax error before `XMesaDisplay' > > > ../include/GL/xmesa_x.h:39: warning: type defaults to `int' > > in declaration > > > of `X > > > MesaDisplay' > > > ../include/GL/xmesa_x.h:39: warning: data definition has no > > type or storage > > > clas > > > s > > > ../include/GL/xmesa_x.h:40: syntax error before `XMesaPixmap' > > > ../include/GL/xmesa_x.h:40: warning: type defaults to `int' > > in declaration > > > of `X > > > MesaPixmap' > > > ../include/GL/xmesa_x.h:40: warning: data definition has no > > type or storage > > > clas > > > s > > > ../include/GL/xmesa_x.h:41: syntax error before `XMesaColormap' > > > ../include/GL/xmesa_x.h:41: warning: type defaults to `int' > > in declaration > > > of `X > > > MesaColormap' > > > ../include/GL/xmesa_x.h:41: warning: data definition has no > > type or storage > > > clas > > > s > > > ../include/GL/xmesa_x.h:42: syntax error before `XMesaDrawable' > > > ../include/GL/xmesa_x.h:42: warning: type defaults to `int' > > in declaration > > > > -- > > Kent Stewart > > Richland, WA > > > > mailto:kbstew99@hotmail.com > > http://kstewart.urx.com/kstewart/index.html > > FreeBSD News http://daily.daemonnews.org/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A11CC69.9F0A3023>