Summary: | kde-base/kimgio-4.11.1 failes to build with error: No rule to make target `install' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marco Clocchiatti <ziapannocchia> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
build.log with MAKEOPTS="-j1" build.log with debug emerge option a build.log again, with no tmp PORTAGE_TMPDIR and debug emerge option |
Description
Marco Clocchiatti
2013-10-03 05:05:45 UTC
Created attachment 360006 [details]
build log
Two things of note: - "tar extract command failed at least partially - continuing anyway" - the plugin doesn't seem to be extracted at all (no webp check) - a build log with '-s' in MAKEOPTS usually is of little use Created attachment 360084 [details]
build.log with MAKEOPTS="-j1"
(In reply to Marco Clocchiatti from comment #3) > Created attachment 360084 [details] > build.log with MAKEOPTS="-j1" Better. Now add '-d' to emerge options - this will make the log significantly larger, but as yet again "tar extract command failed at least partially" we might see why exactly is it failing. Though, what are the chances that you gave not enough disk space for your VM ? Created attachment 360098 [details]
build.log with debug emerge option
that's a better build.log again.
I' don't know if the warn about is really relevant.
On another gentoo box (64-bit), kimgio compiles fine despite of the same warn.
anyway:
ezio ~ # df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 3.8G 3.4G 101M 98% /
udev 10M 4.0K 10M 1% /dev
/dev/vda2 3.8G 3.4G 101M 98% /
tmpfs 203M 340K 203M 1% /run
shm 1013M 0 1013M 0% /dev/shm
cgroup_root 10M 0 10M 0% /sys/fs/cgroup
ramtmp 1013M 1.5M 1011M 1% /tmp/ramtmp
/dev/vdb2 30G 8.3M 28G 1% /usr/portage/distfiles
ezio ~ # ls -l /usr/portage/distfiles/kde-runtime-4.11.1.tar.xz
-rw-rw-r-- 1 portage portage 7973404 Sep 3 22:21 /usr/portage/distfiles/kde-runtime-4.11.1.tar.xz
I think disk space should be enough.
look at /tmp/ramtmp, where it's setted my PORTAGE_TMPDIR: it's 1G disk space.
Please sync the tree, 4.11.2 is in tree. Builds fine for me and can't reproduce the bug. If you have the same error try without ramdisk. As it seems it's following command that fails: tar -xpf /tmp/ramtmp/.emu/portage/kde-base/kimgio-4.11.1/distdir/kde-runtime-4.11.1.tar.xz --xz kde-runtime-4.11.1/cmake/ kde-runtime-4.11.1/CMakeLists.txt kde-runtime-4.11.1/ConfigureChecks.cmake kde-runtime-4.11.1/config.h.cmake kde-runtime-4.11.1/kimgio kde-runtime-4.11.1/cmake/modules/ kde-runtime-4.11.1/CTestConfig.cmake kde-runtime-4.11.1/config-runtime.h.cmake you could check it manually, but given it's a ramdisk, chances are it's a resource conflict - unpacking xz archives on occasions may take a nice chunk of memory. It could also be some kind of permission problem. Also, does ramdisk allow symlinks ? If not, combined size of the archive and the memory reqs of xz might have been too much. sorry if I reopen this bug, but my issue happens again with kimgio-4.11.2 and without tmpdir. ezio kimgio-4.11.2 # grep TMPDIR /etc/portage/make.conf #PORTAGE_TMPDIR="/tmp/ramtmp/.emu" PORTAGE_TMPDIR="/usr/portage/distfiles/fakeTmpDir" ezio kimgio-4.11.2 # df -h Filesystem Size Used Avail Use% Mounted on rootfs 3.8G 3.4G 90M 98% / udev 10M 4.0K 10M 1% /dev /dev/vda2 3.8G 3.4G 90M 98% / tmpfs 203M 352K 203M 1% /run shm 1013M 0 1013M 0% /dev/shm cgroup_root 10M 0 10M 0% /sys/fs/cgroup 192.168.0.12:/var/gentoo-var/distfiles 50G 41G 6.7G 86% /usr/portage/distfiles now, I'm using a nfs tmpdir with more than 6G. kimgio is the only ebuild not working in my system, and this error is really funny Created attachment 360666 [details]
a build.log again, with no tmp PORTAGE_TMPDIR and debug emerge option
It seems that once again unpacking fails. Do check what happens, when that unpacking command is run manually. ezio distdir # pwd /usr/portage/distfiles/fakeTmpDir/portage/kde-base/kimgio-4.11.2/distdir ezio distdir # ls -l kde-runtime-4.11.2.tar.xz lrwxrwxrwx 1 root root 48 Oct 11 21:48 kde-runtime-4.11.2.tar.xz -> /usr/portage/distfiles/kde-runtime-4.11.2.tar.xz ezio distdir # sha256sum /usr/portage/distfiles/kde-runtime-4.11.2.tar.xz 045f38375be1c6c0753a6fc85e7211d3d2dadc974ffc3848920ebfa5d0569df0 /usr/portage/distfiles/kde-runtime-4.11.2.tar.xz ezio distdir # grep -rH kde-runtime /usr/portage/kde-base/kimgio/Manifest /usr/portage/kde-base/kimgio/Manifest:DIST kde-runtime-4.11.2.tar.xz 7974692 SHA256 045f38375be1c6c0753a6fc85e7211d3d2dadc974ffc3848920ebfa5d0569df0 SHA512 21ecca605d94215d6fa68d1b988a8c2c5efeba7ec264bf9ac607462577d3dac0321b4b09af55078a8bc556b2dd68e53c1a4163c87a0300e1c4bff945f71f9396 WHIRLPOOL 14c05b1554eeda1466640dd3f70a2284180bf223f208123e565e420d9cc2f024dae0464a42a9c11b8f996d87d2f52c48f7973f357673cf5c2d3b637484a7c0b9 ezio distdir # tar -xpf kde-runtime-4.11.2.tar.xz --xz kde-runtime-4.11.1/cmake/ kde-runtime-4.11.1/CMakeLists.txt kde-runtime-4.11.1/ConfigureChecks.cmake kde-runtime-4.11.1/config.h.cmake kde-runtime-4.11.1/kimgio kde-runtime-4.11.1/cmake/modules/ kde-runtime-4.11.1/CTestConfig.cmake kde-runtime-4.11.1/config-runtime.h.cmake tar: kde-runtime-4.11.1/cmake: Not found in archive tar: kde-runtime-4.11.1/CMakeLists.txt: Not found in archive tar: kde-runtime-4.11.1/ConfigureChecks.cmake: Not found in archive tar: kde-runtime-4.11.1/config.h.cmake: Not found in archive tar: kde-runtime-4.11.1/kimgio: Not found in archive tar: kde-runtime-4.11.1/cmake/modules: Not found in archive tar: kde-runtime-4.11.1/CTestConfig.cmake: Not found in archive tar: kde-runtime-4.11.1/config-runtime.h.cmake: Not found in archive tar: Exiting with failure status due to previous errors *Ahem*, adjust the command beforehand - why did you expect kde-runtime-4.11.1 dir in kde-runtime-4.11.2 tarball ? If one were there, it would just mean upstream mispackaged it. ops. simply cutting and pasting your command is wrong, because now I'm using a different kde-runtime version. :) now, I cut and paste line 10900 directly from my build.log, and this is the ouput: ezio distdir # tar -xpf /usr/portage/distfiles/fakeTmpDir/portage/kde-base/kimgio-4.11.2/distdir/kde-runtime-4.11.2.tar.xz --xz kde-runtime-4.11.2/cmake/ kde-runtime-4.11.2/CMakeLists.txt kde-runtime-4.11.2/ConfigureChecks.cmake kde-runtime-4.11.2/config.h.cmake kde-runtime-4.11.2/kimgio kde-runtime-4.11.2/cmake/modules/ kde-runtime-4.11.2/CTestConfig.cmake kde-runtime-4.11.2/config-runtime.h.cmake tar: kde-runtime-4.11.2/ConfigureChecks.cmake: Not found in archive tar: kde-runtime-4.11.2/config.h.cmake: Not found in archive tar: kde-runtime-4.11.2/cmake/modules: Not found in archive tar: Exiting with failure status due to previous errors really something seems missing. Despite of the error message, the modules dir is extracted the same: ezio distdir # ls kde-runtime-4.11.2/cmake/modules/ CMakeLists.txt COPYING-CMAKE-SCRIPTS FindCLucene.cmake FindLibSSH.cmake FindQNtrack.cmake FindSLP.cmake MacroDBusAddActivationService.cmake Which version of media-libs/libwebp do you have? (In reply to Michael Palimaka (kensington) from comment #14) > Which version of media-libs/libwebp do you have? It doesn't seem to be a problem with libwebp. It's more like something goes wrong during unpacking. First of all, it's "tar: kde-runtime-4.11.2/cmake/modules: Not found in archive". This dir should be present (though it gets unpacked, as kde-runtime-4.11.2/cmake comes first). The other two may indeed not exist. I suspect kde-runtime-4.11.2/kimgio simply doesn't get unpacked, cause unpacking gets interrupted by previous errors. Therefore no libwebp check. (In reply to Rafał Mużyło from comment #15) > It doesn't seem to be a problem with libwebp. > It's more like something goes wrong during unpacking. More information is better than less. Half of KDE produces a "tar extract command failed at least partially - continuing anyway" message due to eclass artifacts. (In reply to Michael Palimaka (kensington) from comment #16) > (In reply to Rafał Mużyło from comment #15) > > It doesn't seem to be a problem with libwebp. > > It's more like something goes wrong during unpacking. > > More information is better than less. sorry for my delay: ezio ~ # eix libwe [I] media-libs/libwebp Available versions: 0.2.1 ~0.3.0 0.3.1 {abi_mips_n32 abi_mips_n64 abi_mips_o32 abi_x86_32 abi_x86_64 abi_x86_x32 experimental gif +jpeg opengl +png static-libs swap-16bit-csp tiff} Installed versions: 0.3.1(17:08:42 09/30/13)(abi_x86_32 jpeg png -abi_mips_n32 -abi_mips_n64 -abi_mips_o32 -abi_x86_64 -abi_x86_x32 -experimental -gif -opengl -static-libs -swap-16bit-csp -tiff) Homepage: http://code.google.com/p/webp/ Description: A lossy image compression format wonderfull! downgrading to libwebp-0.2.1, kimgio compiles fine. upgrading again to libwebp-0.3.1, the problems doesn't appire anymore. thank's a lot for your support. |