From owner-freebsd-ports Thu Jun 22 19: 3:20 2000 Delivered-To: freebsd-ports@freebsd.org Received: from server1.mich.com (server1.mich.com [198.108.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 0947E37B566 for ; Thu, 22 Jun 2000 19:03:10 -0700 (PDT) (envelope-from will@almanac.yi.org) Received: from argon.gryphonsoft.com (pm014-041.dialup.bignet.net [64.79.82.153]) by server1.mich.com (8.9.3/8.9.3) with ESMTP id WAA26639; Thu, 22 Jun 2000 22:03:04 -0400 Received: by argon.gryphonsoft.com (Postfix, from userid 1000) id 92A59195F; Thu, 22 Jun 2000 22:01:25 -0400 (EDT) Date: Thu, 22 Jun 2000 22:01:25 -0400 From: Will Andrews To: kde-devel@kde.org, FreeBSD Ports Subject: KDE 1.91 problems Message-ID: <20000622220125.A67587@argon.gryphonsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi kde-devel and -ports, I know it's probably too late to be reporting bugs in kde 1.91, but I'm going to do this anyway (if someone tells me to try a CVS build, that is what I will do). I have been trying to update the FreeBSD ports/packages to use KDE 1.91 for 2 weeks now. However, I keep running into many roadblocks. For example, when I run the make for kdelibs, the configure script states that it will build shared libs. However, it fails to build shlibs for kio_*, arts[backend,dsp], kcm_arts, etc. etc. This in turn affects kdebase, kdegames, kdenetwork, and others. Perhaps there is something obvious that I am missing. I have posted the updated ports on my webspace: http://people.FreeBSD.org/~will/kde2/ There are some rather unusual build errors in kdenetwork in particular. There seem to be a number of constants used there that don't exist in FreeBSD. I patched several before giving up on trying to build it. The patches are included in the port above. Also, if you're going to try to use the ports, be warned that not all of their PLISTs were updated.. and if you succeed in building the appropriate shlibs mentioned above, you'll get PLIST errors for sure. On another subject, The configure scripts need to be a little more configurable. For example, we should be able to override the default value of LIBQT in the environment, i.e.: LIBQT="-lqt2" ./configure --[args..], or allow a configure argument for such a thing. Same with other libs, like -ljpeg. It would also be nice to allow adding specific places to look for these libraries, i.e. --with-jpeg-prefix. Of course, --with-extra-libs does this job just fine.. I'd be happy to write the necessary autoconf magic too, or any necessary code if it is determined there's a better way to do this. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message