Now that the ui-tqt problem is fixed, I tried again building the core packages. tqtinterface, arts, kdelibs, and kdebase build without errors. From there seems everything is broken. :(
All of the following packages are still built with automake. I want to get the core packages built so I can help with test bug fixes next weekend.
=========================================== PyKDE3
I previously posted a message that I can't build PyKDE3.
Link to build log:
http://humanreadable.nfshost.com/files/pykde3-3.16.7-i486-1-build.log.gz
=========================================== kdebindings.
Link to build log:
http://humanreadable.nfshost.com/files/kdebindings-3.5.13-i486-svn_1224257-b...
I tried building without sip or pyqt3 installed to ensure there was no presumed python support. kdebindings still failed to build.
=========================================== kdeaccessibility
Link to build log:
http://humanreadable.nfshost.com/files/kdeaccessibility-3.5.13-i486-svn_1224...
=========================================== kdeutils
Link to build log:
http://humanreadable.nfshost.com/files/kdeutils-3.5.13-i486-svn_1224257-buil...
=========================================== kdemultimedia
Link to build log:
http://humanreadable.nfshost.com/files/kdemultimedia-3.5.13-i486-svn_1224257...
===========================================
At this point I stopped. Perhaps the failures are all related.
Darrell
On Wednesday 09 March 2011 23:09:44 Darrell Anderson wrote:
Now that the ui-tqt problem is fixed, I tried again building the core packages. tqtinterface, arts, kdelibs, and kdebase build without errors. From there seems everything is broken. :(
[...]
I think you must set path to tqt include directory, like:
export CXXFLAGS="-I/path/to/tqt/includes"
Maybe the same will be needed for LDFLAGS, for libraries.
I don't pretend to understand the nuances of building software, but the build scripts work fine with the 3.5.12 source tarballs. Something else happened since then.
Darrell
--- On Wed, 3/9/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] Numerous FTBFS Problems To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, March 9, 2011, 3:17 PM On Wednesday 09 March 2011 23:09:44 Darrell Anderson wrote:
Now that the ui-tqt problem is fixed, I tried again
building the core
packages. tqtinterface, arts, kdelibs, and kdebase
build without errors.
From there seems everything is broken. :(
[...]
I think you must set path to tqt include directory, like:
export CXXFLAGS="-I/path/to/tqt/includes"
Maybe the same will be needed for LDFLAGS, for libraries.
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Wednesday 09 March 2011 23:35:53 Darrell Anderson wrote:
I don't pretend to understand the nuances of building software, but the build scripts work fine with the 3.5.12 source tarballs. Something else happened since then.
Sorry, I can't help you more on this matter, my autohell knowledge are minimal either :)
Tim?
Darrell
--- On Wed, 3/9/11, Serghei Amelian serghei@thel.ro wrote:
From: Serghei Amelian serghei@thel.ro Subject: Re: [trinity-devel] Numerous FTBFS Problems To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, March 9, 2011, 3:41 PM On Wednesday 09 March 2011 23:35:53 Darrell Anderson wrote:
I don't pretend to understand the nuances of building
software, but the
build scripts work fine with the 3.5.12 source
tarballs. Something else
happened since then.
Sorry, I can't help you more on this matter, my autohell knowledge are minimal either :)
-- Serghei
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Yes, as far as I know.
tqtinterface, arts, kdelibs, and kdebase build fine, but they all build using cmake.
Based upon what you say, I'm guessing I missed a memo somewhere and don't have my build scripts updated correctly. Let me know how to troubleshoot further.
Darrell
--- On Wed, 3/9/11, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] Numerous FTBFS Problems To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, March 9, 2011, 3:51 PM
Tim?
Looks like something isn't finding TQt. Have you installed the latest versions of everything, including TQt, from SVN after building them utilizing Automake?
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Yes, as far as I know.
tqtinterface, arts, kdelibs, and kdebase build fine, but they all build using cmake.
I'm not convinced that you can successfully build Automake-based packages on top of CMake-built base packages. Any thoughts on that Serghei?
Either way I am also attempting a rebuild, so let me see if I run into anything similar as I build the core system.
Tim
On Thursday 10 March 2011 01:15:48 Timothy Pearson wrote:
Yes, as far as I know.
tqtinterface, arts, kdelibs, and kdebase build fine, but they all build using cmake.
I'm not convinced that you can successfully build Automake-based packages on top of CMake-built base packages. Any thoughts on that Serghei?
Should be ok, cmake/automake installing files in same way.
Either way I am also attempting a rebuild, so let me see if I run into anything similar as I build the core system.
Tim
I'm in the process of building 3.5.12 from source tarballs. That will let me know whether my build scripts are the problem.
Darrell
--- On Wed, 3/9/11, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] Numerous FTBFS Problems To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, March 9, 2011, 5:15 PM
Yes, as far as I know.
tqtinterface, arts, kdelibs, and kdebase build fine,
but they all build
using cmake.
I'm not convinced that you can successfully build Automake-based packages on top of CMake-built base packages. Any thoughts on that Serghei?
Either way I am also attempting a rebuild, so let me see if I run into anything similar as I build the core system.
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
I tested my build scripts with the 3.5.12 source tarballs. That meant building only with automake and not cmake.
This is on Slackware 12.2 with autoconf 2.63, automake 1.10.1, and qt-3.3.8c.
I built the following 3.5.12 packages without errors with automake.
tqtinterface arts kdelibs kdebase sip (upstream sources) pyqt3 (upstream sources) pykde3 (upstream sources) kdebindings kdeaccessibility kdeutils kdemultimedia kdenetwork kdeadmin kdeartwork kdegames kdetoys kdeedu kdegraphics kdevelop kdeaddons kdewebdev libical libcaldav kdepim kdesdk k3b amarok knemo koffice gtk-qt-engine ksystemlog kaffeine k9copy
Package sizes are very close to those I created last autumn.
So what causes my build scripts to fail to build from svn with automake?
Darrell
--- On Wed, 3/9/11, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] Numerous FTBFS Problems To: trinity-devel@lists.pearsoncomputing.net Date: Wednesday, March 9, 2011, 5:15 PM
Yes, as far as I know.
tqtinterface, arts, kdelibs, and kdebase build fine,
but they all build
using cmake.
I'm not convinced that you can successfully build Automake-based packages on top of CMake-built base packages. Any thoughts on that Serghei?
Either way I am also attempting a rebuild, so let me see if I run into anything similar as I build the core system.
Tim
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Darrell Anderson -
Serghei Amelian -
Timothy Pearson