You are not logged in.
There is a possible problem that has to do with linking, regarding the current toolchain.
The problem must have been introduced after 02-05-2010 (2 May 2010).
I will explain.
I am one of the maintainers of the adslgr64 repo, and one of the packages I am building regularly is k3b-svn (about 2-3 times per week).
I get an svn source tarball like this (these are lines from a bash script that I use):
svn co ${_svntrunk} ${_svnmod}
rm -rf aut*
rm -f config
rm -f README.txt
rm -f servers
tar -cvJpsSf ~/downloads/${_svnfilename}-${_svnrevision}.tar.xz ./
And then the PKGBUILD I am using is this:
pkgname=k3b-svn
realname=k3b
pkgver=1121856
pkgrel=1
lateststablever=1.91
pkgdesc="Feature-rich and easy to handle CD burning application"
tarname=k3b-svn
arch=("i686" "x86_64")
license=('GPL')
url="http://k3b.sourceforge.net/"
depends=('kdebase-runtime>=4.4.0' 'kdemultimedia-kioslave>=4.4.0' 'libsamplerate'
'libmad' 'ffmpeg>=23065' 'taglib>=1.4' 'libmpcdec>=1.2.5' 'libdvdread>=4.1.3'
'cdrdao' 'cdrkit')
makedepends=('cmake' 'pkgconfig' 'automoc4' )
optdepends=('dvd+rw-tools: for dvd burning support'
'vcdimager: for vcd burning support'
'transcode: for advanced mpeg conversion support'
'emovix: for bootable multimedia cd/dvd support')
options=(!libtool)
conflicts=('k3b')
provides=("k3b=${lateststablever}")
install=${pkgname}.install
source=(${sourcetarballdir}/${tarname}-${pkgver}.tar.xz)
build() {
cd ${srcdir}/${realname}
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release \
-DCMAKE_SKIP_RPATH=ON -DCMAKE_{SHARED,MODULE,EXE}_LINKER_FLAGS='-Wl,--no-undefined -Wl,--as-needed'
make || return 1
make DESTDIR=${pkgdir} install || return 1
}
The last time I was able to finish a build successfully was on the date I mention above.
After that, every newest svn build exists at the same spot with the same linking error:
[ 92%] Building CXX object src/CMakeFiles/k3b_bin.dir/rip/videodvd/k3bvideodvdtitlemodel.o
Linking CXX executable k3b
[ 92%] Built target k3b_bin
make: *** [all] Error 2
The same happens if I slightly alter the PKGBUILD:
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release
I tried to rebuild today the same svn revision I had successfully built 10 days ago, and it also fails with the same linking error at the same spot.
So logic dictates that there has to be a problem in the building toolchain that has to do with linking. And that problem was introduced some time after 02-05-2010.
Any proposals would be greatly appreciated.
Thank you for you time.
Last edited by wantilles (2010-05-23 10:18:42)
Offline
Run cmake with the verbose flags so we can see the actual error message.
Offline
Run cmake with the verbose flags so we can see the actual error message.
How do I do that?
I just checked the cmake man page, and there no relevant information.
Offline
Do a "make VERBOSE=1 || return 1" in the PKGBUILD.
Offline
Does this happen on both architectures?
Offline
Does this happen on both architectures?
I can only tell about x86_64.
Here is the verbose error output:
cd ~/temp/k3b-svn-1121856-2/src/k3b/src && /usr/bin/cmake -D_filename=~/temp/k3b-svn-1121856-2/src/k3b/src/k3b_bin.shell -D_library_path_variable=LD_LIBRARY_PATH -D_ld_library_path="~/temp/k3b-svn-1121856-2/src/k3b/lib/./:/usr/lib:/usr/lib:/usr/lib" -D_executable=~/temp/k3b-svn-1121856-2/src/k3b/src/k3b_bin -P /usr/share/apps/cmake/modules/kde4_exec_via_sh.cmake
make[2]: Leaving directory `~/temp/k3b-svn-1121856-2/src/k3b'
/usr/bin/cmake -E cmake_progress_report ~/temp/k3b-svn-1121856-2/src/k3b/CMakeFiles 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80
[ 92%] Built target k3b_bin
make[1]: Leaving directory `~/temp/k3b-svn-1121856-2/src/k3b'
make: *** [all] Error 2
==> ERROR: Build Failed.
Aborting...
Offline
It still does not show the actual error message... stupid cmake hiding everything!
Offline
The problem solved itself after about a week (about a week ago) with no further intervention from my part.
Checking my pacman.log on which packages were updated between these two points in time (the point where the problem presented itself and the point it went away), I think k3b-svn might have had linking issues with KDE 4.4.3 for about a week.
Offline