22 Feb
2011
22 Feb
'11
1:58 p.m.
Calvin wrote:
On an Intel Atom it takes much longer than 5 minutes :P It broke again D:
Do you think it is related to the environmental variables?
Hmmm..
(1.) The very first thing I want to do is confirm that you have the following
built and installed in this order, so show us 'pacman -Q | grep trinity':
15:34 supersff:~> pacman -Q | grep trinity # then I manually sorted
trinity-qt3 3.3.8-20
trinity-pyqt3 3.18.1-9
trinity-tqtinterface 1221148-1
trinity-arts 1214641-1
trinity-kdelibs 1222098-1
Your stuck at 37% on
trinity-kdebase 1221588-1
(2.) Please post the error you received after rebuilding with 'make VERBOSE=1'
in the build() function. (it will provide a little more info that will help)
Your environment for the build is set within the PKGBUILD file so it shouldn't
matter what your existing shell environment is:
export CMAKE_PREFIX_PATH=/opt/qt:/opt/trinity
CMAKE_INCLUDE_PATH=/opt/qt/include:/opt/qt/include/tqt:/usr/include/dbus-1.0:/opt/trinity/include:/opt/trinity/include/libkrandr
export LD_LIBRARY_PATH=/opt/trinity/lib:/opt/trinity/lib/kde3:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=:/opt/trinity/lib/pkgconfig:/opt/qt/lib/pkgconfig
The build environment will be influenced by
/etc/ld.so.conf.d/trinity-kdelibs.conf. So if you have trinity-kdelibs installed:
(3.) confirm you have
cat /etc/ld.so.conf.d/trinity-kdelibs.conf
/opt/trinity/lib
(4.) As root, run ldconfig if the trinity-kdelibs.conf so the linker cache
magic is updated.
What I want to confirm is that you are NOT trying to build on a system with
KDE4/Qt4 or kdemod3 installed. That will screw up your build because of the
conflicting libraries that cmake has trouble ignoring. So:
(5.) look at:
pacman -Q | grep "qt\|kde"
If you have:
qt 4.7.1-3
kdemod3-<anything> 3.5.10-1
kde<xyz>-<anything> 4.6.0-2
The build will fail.
I don't know how a build between a normal i686, x86_64 and an Intel Atom will
differ, but I haven't heard anything that says building on an Intel Atom won't
work -- or that it *will* work for that matter. So let's take it step by step.
Change into
trinity-qt3
do 'makepkg -sf --noextract' to do a quick rebuild of the existing package and
install it with 'sudo pacman -U trinity-qt3-<version>.xz.
do the same thing for trinity-pyqt3
Change into
trinity-tqtinterface - a simple makepkg -sf and install with 'sudo pacman -U
trinity-tqtinterface-<version>.xz.
Do the same thing for 'trinity-arts' and 'trinity-kdelibs'. After
'trinity-kdelibs' is installed - and run (as root) ldconfig.
(6.) Change into
trinity-kdebase - and restart the build with 'make VERBOSE=1' and post the
output if it fails again.
I'm scratching my head on this one. I've literally built Trinity 5-6 times in
the past 2 days using the build script and gotten no errors during the make. So
the PKGBUILDs work. If there is something special we need to do for the Intel
Atom, then that's something we will have to look into. But, to get started, we
need the information requesting in (1.) - (6.) above :)
--
David C. Rankin, J.D.,P.E.