Ok so i have successfully compiled the base of Trinity using Qt3 and everything in /usr. A while back i also successfully compiled many of the 'applications' from the applications folder. Today i am having no such luck.
I am pushing out a release candidate of Porteus this weekend with a 'skin & bones' version of Trinity that successfully compiled a few weeks ago. The problem is that koffice is no longer compiling for me, and neither is k3b.
I have booted using the Trinity-3.5.13 that i compiled and when trying to build k3b, here is my output.
In file included from k3bglobals.cpp:28:0: /usr/include/tdeversion.h:57:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:64:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:71:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:78:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:84:5: error: ‘TDECORE_EXPORT’ does not name a type k3bglobals.cpp: In function ‘KIO::filesize_t K3b::imageFilesize(const KURL&)’: k3bglobals.cpp:304:126: warning: ‘static bool KIO::NetAccess::exists(const KURL&, bool)’ is deprecated (declared at /usr/include/kio/netaccess.h:282) k3bglobals.cpp: In function ‘bool K3b::mount(K3bDevice::Device*)’: k3bglobals.cpp:601:74: warning: converting ‘false’ to pointer type for argument 1 of ‘QString::QString(const char*)’ make[3]: *** [k3bglobals.lo] Error 1 make[3]: Leaving directory `/tmp/k3b/libk3b/core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/k3b/libk3b' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/k3b' make: *** [all] Error 2
Hoping someone more intelligent than i can point m in the right direction.
J
Ok so i have successfully compiled the base of Trinity using Qt3 and everything in /usr. A while back i also successfully compiled many of the 'applications' from the applications folder. Today i am having no such luck.
I am pushing out a release candidate of Porteus this weekend with a 'skin & bones' version of Trinity that successfully compiled a few weeks ago. The problem is that koffice is no longer compiling for me, and neither is k3b.
I have booted using the Trinity-3.5.13 that i compiled and when trying to build k3b, here is my output.
In file included from k3bglobals.cpp:28:0: /usr/include/tdeversion.h:57:5: error: ‘TDECORE_EXPORT’ does not name a type
/usr/include/tdeversion.h:64:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:71:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:78:5: error: ‘TDECORE_EXPORT’ does not name a type
/usr/include/tdeversion.h:84:5: error: ‘TDECORE_EXPORT’ does not name a type k3bglobals.cpp: In function ‘KIO::filesize_t K3b::imageFilesize(const KURL&)’: k3bglobals.cpp:304:126: warning: ‘static bool KIO::NetAccess::exists(const KURL&, bool)’ is deprecated (declared at /usr/include/kio/netaccess.h:282)
k3bglobals.cpp: In function ‘bool K3b::mount(K3bDevice::Device*)’: k3bglobals.cpp:601:74: warning: converting ‘false’ to pointer type for argument 1 of ‘QString::QString(const char*)’ make[3]: *** [k3bglobals.lo] Error 1
make[3]: Leaving directory `/tmp/k3b/libk3b/core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/k3b/libk3b' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/k3b'
make: *** [all] Error 2
I haven't tried building 3.5.13 for a while, but you can find my build scripts and packages at my web site (http://humanreadable.nfshost.com/trinity/).
A note about koffice that stumped me for a long time: koffice requires more than 2GB of temporary space to build. In my entire Slackware build respository, I build all but a few packages in $TMP, which is assigned to tmpfs, which on my system is 2GB free space (I have 4GB of RAM). When I finally figured out koffice was always failing to build because of running out of build space, I was able to build koffice thereafter.
A long time ago I submitted an enhancement request to break koffice into individual packages.
Contrarily, I never had a problem building k3b on Slackware. Glancing at the errors you posted indicates something is awry with both the core and k3b sources. Those k3b references to Qstring should be TQString. That indicates possibly using KDE 3.5.10 sources.
Another confusion is you say you are building 3.5.13. The renaming project started after 3.5.13 was released and tdeversion.h was named kdeversion.h in 3.5.13. Also in 3.5.13, TDECORE_EXPORT would have been KDECORE_EXPORT in kdeversion.h.
My first guess is you have GIT sources mixed with 3.5.13 sources, and maybe 3.5.10 sources too.
You can find the 3.5.13 source tarballs here (http://trinity.blackmag.net/releases/3.5.13/).
I hope that helps. :)
Darrell
Thanks for the explanation. I know for sure that memory is not the problem. You are right about the confusion of terminology ... i am pulling from git. The only time i mix sources is grabbing the slack-desc file from the tarballs.
I think i will start from the beginning again using the tarballs and slackbuilds and see how things pan out. Thanks Darrell, i have found your slackbuilds invaluable.
Jay
On Sat, Feb 18, 2012 at 5:27 PM, Darrell Anderson humanreadable@yahoo.comwrote:
Ok so i have successfully compiled the base of Trinity using Qt3 and everything in /usr. A while back i also successfully compiled many of the 'applications' from the applications folder. Today i am having no such luck.
I am pushing out a release candidate of Porteus this weekend with a 'skin & bones' version of Trinity that successfully compiled a few weeks ago. The problem is that koffice is no longer compiling for me, and neither is k3b.
I have booted using the Trinity-3.5.13 that i compiled and when trying to build k3b, here is my output.
In file included from k3bglobals.cpp:28:0: /usr/include/tdeversion.h:57:5: error: ‘TDECORE_EXPORT’ does not name a type
/usr/include/tdeversion.h:64:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:71:5: error: ‘TDECORE_EXPORT’ does not name a type /usr/include/tdeversion.h:78:5: error: ‘TDECORE_EXPORT’ does not name a type
/usr/include/tdeversion.h:84:5: error: ‘TDECORE_EXPORT’ does not name a type k3bglobals.cpp: In function ‘KIO::filesize_t K3b::imageFilesize(const KURL&)’: k3bglobals.cpp:304:126: warning: ‘static bool KIO::NetAccess::exists(const KURL&, bool)’ is deprecated (declared at /usr/include/kio/netaccess.h:282)
k3bglobals.cpp: In function ‘bool K3b::mount(K3bDevice::Device*)’: k3bglobals.cpp:601:74: warning: converting ‘false’ to pointer type for argument 1 of ‘QString::QString(const char*)’ make[3]: *** [k3bglobals.lo] Error 1
make[3]: Leaving directory `/tmp/k3b/libk3b/core' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/k3b/libk3b' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/k3b'
make: *** [all] Error 2
I haven't tried building 3.5.13 for a while, but you can find my build scripts and packages at my web site ( http://humanreadable.nfshost.com/trinity/).
A note about koffice that stumped me for a long time: koffice requires more than 2GB of temporary space to build. In my entire Slackware build respository, I build all but a few packages in $TMP, which is assigned to tmpfs, which on my system is 2GB free space (I have 4GB of RAM). When I finally figured out koffice was always failing to build because of running out of build space, I was able to build koffice thereafter.
A long time ago I submitted an enhancement request to break koffice into individual packages.
Contrarily, I never had a problem building k3b on Slackware. Glancing at the errors you posted indicates something is awry with both the core and k3b sources. Those k3b references to Qstring should be TQString. That indicates possibly using KDE 3.5.10 sources.
Another confusion is you say you are building 3.5.13. The renaming project started after 3.5.13 was released and tdeversion.h was named kdeversion.h in 3.5.13. Also in 3.5.13, TDECORE_EXPORT would have been KDECORE_EXPORT in kdeversion.h.
My first guess is you have GIT sources mixed with 3.5.13 sources, and maybe 3.5.10 sources too.
You can find the 3.5.13 source tarballs here ( http://trinity.blackmag.net/releases/3.5.13/).
I hope that helps. :)
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I think i will start from the beginning again using the tarballs and slackbuilds and see how things pan out. Thanks Darrell, i have found your slackbuilds invaluable.
Thanks for the compliment. :)
FYI: My old build scripts at my web site supported both KDE3 and TDE. In other words, they can be challenging to follow because of the dual support. My new scripts only support TDE. I need to get those uploaded real soon now that I have successfully built from GIT several times....
Darrell
I picked through the old scripts and modified to suit my needs. Will be anxiously awaiting the more current build scripts.
Thanks.
Jay
On Sat, Feb 18, 2012 at 8:34 PM, Darrell Anderson humanreadable@yahoo.comwrote:
I think i will start from the beginning again using the tarballs and slackbuilds and see how things pan out. Thanks Darrell, i have found your slackbuilds invaluable.
Thanks for the compliment. :)
FYI: My old build scripts at my web site supported both KDE3 and TDE. In other words, they can be challenging to follow because of the dual support. My new scripts only support TDE. I need to get those uploaded real soon now that I have successfully built from GIT several times....
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I picked through the old scripts and modified to suit my needs. Will be anxiously awaiting the more current build scripts.
I anticipate getting several patches merged soon that I have been working on. When they are merged and I have my local GIT repository synced I can delete those patches from my build environment. Then I will upload my new build environment environment package, which will be much streamlined.
Darrell
-
Darrell Anderson -
Jay