> >> #include <tqevent.h>
> >>
> >> directly before this block of text:
> >>
> >> #include <tqvaluelist.h>
> >> #include <tqwindowdefs.h>
> >> #include <kdelibs_export.h>
> >> #include <X11/Xlib.h>
> >>
> >> Retry the compilation; if it gets farther please
> let me
> >> know.
I added that change to kipc.cpp and kept the same change in kxerrorhandler.h.
I'm curious: why the same change but one in a cpp and the other in an h file. Why not both cpp or h files?
The package compiled for about 20 minutes. That is progress --- the previous failure occurred quickly at about two minutes.
I'm attaching the full build output.
I'm unsure but looks like there are gcc file location errors. I'm using GCC 4.2.4, which is what comes with Slackware 12.2.
Note: I realize the free/libre software world moves at a maddening pace. Some people might consider Slackware 12.2 ancient or obsolete, but actually is more recent than Debian Lenny. Lenny is still supported and will be for a long while yet. I presume the Trinity KDE packages are compatible with Lenny and therefore should be compatible with Slackware 12.2. Also, Lenny and 12.2 were the last distros to support KDE 3.5.10 and I think Trinity should be backwards compatible with those distros --- at least for a long while.
> Yes it does. Can you try this test:
> In the file kdelibs/kdecore/kxerrorhandler.h, insert the
> following line:
>
> #include <tqevent.h>
>
> directly before this block of text:
>
> #include <tqvaluelist.h>
> #include <tqwindowdefs.h>
> #include <kdelibs_export.h>
> #include <X11/Xlib.h>
>
> Retry the compilation; if it gets farther please let me
> know.
Still failed. I'm attaching the output. I verified after the build failed that the file was updated.
Attached are the results of building kdeutils.
Hopefully the results help.
However, I am stopping the build tests based upon your response that building packages requires a successful build and installation of the requisite packages in the build chain.
I will prep a virtual Slackware 12.2 machine. I will try building arts and then kdelibs.
Darrell
I'm continuing to test building other packages.
Please take your time responding.
I'm just testing and forwarding information in the hope that when these builds fail there might be common causes.
kdebindings failed to build. Looks like python issues.
I also notice libtool warnings.
I'm sending an attachment of the build output.
Darrell
I decided to see how other packages might compile. Next in the build chain is kdebase. That build effort failed quickly.
I'm attaching the output of the build.
Curious error message:
configure: WARNING: linux/cdrom.h: present but cannot be compiled
Is this a problem with my kernel version (2.6.27.48-smp) or kernel configuration? I can recompile the kernel if necessary?
I do not have the Trinity version of kdelibs or arts installed. I don't know whether that is important.
I'm building with a stock 3.5.10 installed.
Darrell
I'm attaching a text file of the build output.
Regarding avahi, I just built and installed the avahi 0.6.25 package. Not the latest version, but all I can install because I have an older GTK2 package.
I saw no error messages when trying to build kdelibs with avahi installed. Thus, my concern about Debian-specific package names was unfounded. I notice in the avahi package contents the files your build system seeks are include files, which would be the same on any system.
I installed avahi only to test the build process. I don't think avahi should be a prerequisite and the stock Slackware does not provide that package. Anyway, good news that the build works with or without avahi.
I hope the attached file helps.
Suspect messages I notice in the config process:
lua.h was not found or was not usable, Lua 5.0 headers are required !
...
configure: WARNING: Could not find krb5-config
...
configure: creating ./config.status
wrong input (flag != 4) at admin/conf.change.pl line 117, <> line 1998.
...
config.status: creating kdecore/kde-config.cpp
config.status: WARNING: 'kdecore/kde-config.cpp.in' seems to ignore the --datarootdir setting
D.
> Can you please post the complete output of your build
> script? You can
> attach it to a message as a text document if you want.
I just did with the previous response.
I'll attach again.
> can you please
> post the complete output of the build script in a text
> attachment?
Here you go:
1) Build script is tqtinterface.SlackBuild
2) KDE.options, which is sourced in the build script
3) stdout of build process
I am not building directly within the svn tree. I copy the tqtinterface directory to a build location.
