Le Fri, 4 Nov 2011 18:21:24 -0700 (PDT),
Darrell Anderson <humanreadable@...> a �crit :
> > > Can Trinity be built with those packages installed? Do
> > any of them
> > > have to be removed in the build environment?
> > I did all of my builds with KDE4 installed and running.
> Please send me a copy of your build scripts. I had to delete the KDE4
> and QT4 packages before I started having success building 3.5.13. I
> must be missing something.
I already sent the complete tarball of my scripts to the list; I'm
sending them again, including the kdeetc3 Slackware package I use to
have suitable profile scripts, and which is derived from
As additional information:
-the qt3-png14.diff is no more useful with current qt3-3.3.8d and the
line of the script which uses it *must* be removed (because the patch
won't apply anymore). I didn't update the script in the tarball.
-I just built kdelibs/kdebase/kdepim on a mostly clean Slackware 13.1
installation (with downgraded graphics drivers). I had some minor issues
related to my using the Slackware64 kernel (because of the 6G of RAM),
but otherwise it should work fine (and the issues were generally
solved by setting ARCH=i486/i686). I did reproduce:
-neither your issues about qglobal.h (but I kept the patch I sent before
to try solve this problem applied to my copy of the SVN repo; this patch
-nor my own issue about broken Slackware 13.37 libical
I should add I still have a modified SVN local copy of dbus-tqt: the
patch is attached.
-the build script is the generic script I use to build *all* cmake
packages I built; the usage is
# ./build /path/to/package/source package-name
> I also can't get kdebindings, pyqt3 and pykde3 to build.
I didn't try to build them.
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe@... For additional
> commands, e-mail: trinity-devel-help@... Read
> list messsages on the Web archive:
> http://trinity-devel.pearsoncomputing.net/ Please remember not to