Date: Thu, 23 Aug 2001 09:21:04 -0700 From: Kent Stewart <kstewart@urx.com> To: Idar Tollefsen <Idar.Tollefsen@baerum.kommune.no> Cc: freebsd-questions@freebsd.org Subject: Re: compile KDE2.2 error on FreeBSD Message-ID: <3B852D70.3CCE8884@urx.com> References: <sb84ecc7.088@mail.baerum.kommune.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Idar Tollefsen wrote: > > Kent, > > > When did you cvsup, kappfinder was turned off just > > a few minutes before 19 August. > > Apparently before the 19th then :-) > > No, seriously, I'll do a new cvsup and try again. > My latest cvsup was on the 15th, IIRC. Kdelibs is up to 2.2_1 and so is kdebase. Since they are the basis of everything else, you need to rebuild them. The majority of the changes seen to be creating a proper pkg-plist and dependancy lists. Portupgrade is supposed to care of this but I want to build packages. I do use "portsdb -Uu" to build a current INDEX after each cvsup of ports-all. I build kde-2.2 modules on a dual 866 system and install them by using "make package". I move the packages to my other five computers and pkg_add them. I have kde-2.2 running on 5 different systems right now. One is a Intel Celeron 433a. Building XFree86 or kde-2.2 on that system takes a long time. Package adding kde-2.2 was around 30 minutes of my time. > > I can't quite grasp why KDE2 with dependencies > have -O2 turned on on the Alpha, when it then > proceeds to spew out huge warnings about > how -O2 triggers known optimizer bugs > on this platform for every file it compiles. > > When I saw these warnings, I proceeded > to override it in make.conf. The result was > that the settings in make.conf of course was > picked up and used, but appended to already > existing settings in the ports makefiles. > According to the gcc man pages, the latest > -Ox specified is the one that takes effect. > I therefore trust I haven't compiled it with > -O2, but with -O1. It still complains tough, but > I suspect that's because it sees -O2 as part > of the command at all, disregarding the fact > that another -Ox option has been specified > later. My flags in make.conf are -O -pipe. I don't have any idea on any other choices. > > The reason I rant on about this is because > I'm trying to deduce wether or not the > problems I have are related to some > compiler setting that could be less than > ideal on the Alpha. I always suspected they > were, because I haven't seen any major > complains about it, and I think there would > have been a lot of them if KDE2 was broken > on i386 as well. > > As a side note: what is the procedure when > a port is broken? cvsup - test again - write > to freebsd-ports - contact the maintainer - > file a bug report? I follow -stable and when a new release comes out such as kde-2.2, I follow those changes. > > - IT -- 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?3B852D70.3CCE8884>