10 Mar
2011
10 Mar
'11
6:48 a.m.
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(a)pearsoncomputing.net> wrote:
From: Timothy Pearson
<kb9vqf(a)pearsoncomputing.net>
Subject: Re: [trinity-devel] Numerous FTBFS Problems
To: trinity-devel(a)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(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)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