Hi,
So, with Trinity 3.5.12 nearing, it's time for me to update the BLFS
books with Trinity
and create RPM spec files from them.
So, what configure options did everyone use? I know I mentioned it
before, but it's probably easier to have one central place
so we can compare what options and why.
(Here. :D )
--
later, Robert Xu
After updating my build scripts to support the tarball naming and compression scheme, I started another build run.
kdebase-3.5.12.tar.gz FTBFS.
My apologies for incorrectly referencing kdelibs in a previous post.
I can include a big log, but I think the error is clear:
make[4]: Entering directory `/dev/shm/kdebase/kcontrol/energy/pics'
make[4]: *** No rule to make target `energybig.png', needed by `all-am'. Stop.
make[4]: Leaving directory `/dev/shm/kdebase/kcontrol/energy/pics'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/dev/shm/kdebase/kcontrol/energy'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/dev/shm/kdebase/kcontrol'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/dev/shm/kdebase'
make: *** [all] Error 2
The energybig.png pic is in SVN but not the 3.5.12 tarball. I downloaded that earlier file today. Just to be sure, I again downloaded the tarball a couple of minutes ago and there is no such png file.
Darrell
I have created a set of pre-release source tarballs for Trinity 3.5.12.
They are currently publishing to the mirror, and should be available
within 48 hours from this link:
http://ppa2.quickbuild.pearsoncomputing.net/redirect.php?file=releases/3.5.…
If no issues are found in the next four days, there is a very good chance
these files will become the final release.
Please keep this information on this list for now; I am releasing the
files early for testing purposes only, not for general consumption.
Thanks!
Tim
Hi,
Being that 3.5.12 is on the verge of being released, I've decided to
include this release in BLFS to replace the aging 3.5.10.
Given that KDE 4 has rapidly changed quickly, we can't keep up with
the pace, and that stupid cmake.
I've also decided to build RPMs of the KDE 3.5.12 release. They'll be
built for Mandriva, Fedora, and SuSE :)
What configure options would you recommend for stuff like this?
I saw a thread on trinity-devel, but given the fact that I just
subscribed (when I should have done so earlier -.-"), I don't have the
emails.
--
later, Robert Xu
Hello,
As I see, in kde4 api-dox are not handled anymore by building system (actually
apidox is not handled by autotools anyway in kde3, but by script named
doxygen.sh). Is there any reason to include apidox support in cmake scripts?
--
Serghei
I'm wrapping my head around something new.
In the past I have been copying the svn package contents to tmpfs and working there with my compiles. That habit came from being accustomed to building packages from a source tarball. The source tarball is unpacked to a temporary working area and then compiled. With svn, something to which I am new, I maintained that habit by copying the package contents.
Trinity is huge and compiling the entire core package suite requires 6 hours even on a dual core system. I could live with that if I knew the packages always compiled 100% of the time. That is a normal expectation with tarballs, but is not the case in a dynamic svn environment. There always is some degree of breakage. Hence a previous suggestion to use ccache.
I have compiled kernels for many years. Being new to svn I did not understand that, much like the kernel, I don't have to image package sources from the svn tree but can work directly in that directory. Like the kernel I need only use 'make clean' to restore the svn tree. I then can use ccache to create compiling caches, which should dramatically reduce compile times.
If I understand correctly, then in my build scripts I need to do the following:
================================
WAS:
(snippet from arts package build script)
echo "Copying $PRGNAM source files to $TMP..."
cp -a $SVN_SOURCES/dependencies/$PRGNAM $TMP/ || exit 1
cd $PRGNAM || exit 1
echo
echo "Building make and config files..."
echo
echo "Package will be stored at $OUTPUT."
echo
cp -p "$LIBTOOLM4" admin/libtool.m4.in
cp -p "$LTMAINSH" admin/ltmain.sh
make -f admin/Makefile.common
echo
echo "Finished building make and config files."
echo
chown -R root:root .
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--disable-debug \
--program-prefix="" \
--program-suffix="" \
--build=$ARCH-slackware-linux
make $NUMJOBS || exit 1
make install DESTDIR=$PKG
================================
CHANGE TO:
echo "Changing to $PRGNAM source files in SVN..."
cd $SVN_SOURCES/dependencies/$PRGNAM || exit 1
echo
echo "Building make and config files..."
echo
echo "Package will be stored at $OUTPUT."
echo
cp -p "$LIBTOOLM4" ./admin/libtool.m4.in
cp -p "$LTMAINSH" ./admin/ltmain.sh
make -f ./admin/Makefile.common
echo
echo "Finished building make and config files."
echo
chown -R root:root .
make clean
if [ -x /usr/bin/ccache ]; then
CC="ccache gcc"
echo "Using ccache. Unless configured otherwise, the cache is stored in $HOME/.ccache."
echo
else
CC="gcc"
fi
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
$CC ./configure \
--prefix=${PREFIX} \
--sysconfdir=${SYSCONFDIR} \
--libdir=${LIBDIR} \
--disable-debug \
--program-prefix="" \
--program-suffix="" \
--build=$ARCH-slackware-linux
make $NUMJOBS || exit 1
make install DESTDIR=$PKG
================================
Do I have the correct idea?
Thanks much!
Darrell
I have been thinking how we might provide binary packages for Slackware 12.2
I'm hoping that if binary packages are available, in addition to build scripts at my site, that interest will increase among Slackware users. Although many Slackers build their own packages, many do not. Yet if they can download the final packages they might spark new interest in Trinity.
I don't have the bandwidth at my meager web site to host packages.
You have offered to host packages. How do we want to do this?
If we wait until the official 3.5.12 tarballs are available, I can build those final packages. I just need to get them to you.
We would need to post and test a link at your web site just like the other links.
If we coordinated this then you could include Slackware 12.2 as part of your release announcement.
Darrell
