media-libs/tiff-3.5.7-r1 does not compile or install anything: === Begin screenshot === Calculating dependencies ...done! >>> emerge (1 of 63) media-libs/tiff-3.5.7-r1 to / >>> md5 ;-) tiff-v3.5.7.tar.gz >>> Unpacking source... >>> Unpacking tiff-v3.5.7.tar.gz to /var/tmp/portage/tiff-3.5.7-r1/work >>> Source unpacked. >>> Install tiff-3.5.7-r1 into /var/tmp/portage/tiff-3.5.7-r1/image/ category media-libs man: strip: >>> Completed installing into /var/tmp/portage/tiff-3.5.7-r1/image/ >>> Merging media-libs/tiff-3.5.7-r1 to / >>> Regenerating /etc/ld.so.cache... >>> media-libs/tiff-3.5.7-r1 merged. media-libs/tiff selected: none protected: 3.5.7-r1 omitted: none >>> clean: No packages selected for removal. >>> emerge (2 of 63) media-libs/imlib-1.9.14-r1 to / === End screenshot === Consequently imlib fails to compile. This is on a new system (actually within a chroot on an existing installation) after "emerge system" and installing some additional software. Since imlib depends on tiff and many packages depend on imlib, I'm marking this as a Blocker. Reproducible: Always Steps to Reproduce: 1. emerge media-libs/imlib Actual Results: media-libs/tiff is installed, but contains no files: === Begin screenshot === hybrid portage # qpkg -l tiff media-libs/tiff-3.5.7-r1 * CONTENTS: hybrid portage # === End screenshot === Expected Results: Compile, install and merge libtiff, of course. ;) Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r2) ================================================================= System uname: 2.4.19-hybrid-7 i586 AMD-K6(tm) 3D processor GENTOO_MIRRORS="http://cube.sascha.silbe.org/gentoo ftp://ftp.tu-clausthal.de/pub/linux/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb" CONFIG_PROTECT_MASK="/etc/gconf /etc/afs/C /etc/afs/afsws /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss gnome zlib perl 3dnow acl afs -apm -arts -avi berkdb crypt -cups -encode gdbm -gif -gpm -gtk imlib ipv6 -java jpeg -kde libg++ libwww mikmod mmx -motif mpeg nas ncurses nls oggvorbis -opengl pam pdflib png python -qt -qtmt -quicktime readline -sdl slang spell -sse ssl -svga -tcltk -tcpd tetex truetype X xml2 -xmms -xv" COMPILER="gcc3" CHOST="i586-pc-linux-gnu" CFLAGS="-march=k6" CXXFLAGS="-march=k6" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://hybrid.sascha.silbe.org/gentoo-portage" FEATURES="sandbox ccache"
just so you know, beyond emerge system, you really should reboot into your new gentoo system to emerge things.
I'm trying to set up a copy of the existing server (using Gentoo 1.4_rc3 instead of 1.2). Until everything is installed and set up again, I won't boot this new system, only chroot into it. So what do I need to execute manually (besides env-update) if I chroot into this system instead of booting it?
Can you attach a log of the entire build process? I can't reproduce this problem on my computer.
Created attachment 9854 [details] Build log for "emerge imlib"
Created attachment 10087 [details] modified tiff-3.5.7-r1.ebuild Can you please test this ebuild, and see if the emerge fails when compiling tiff now? I have put || die checks on several of the commands that could be causing problems.
OK, I've found the problem: On the new system /usr/portage/media-libs/tiff-3.5.7-r1.ebuild consists of only binary 0s. Seems like I got a corrupt file from one of the RSYNC servers. Since time and size are exactly the same as the real file, rsync does not replace this file. After adding "-c" (always checksum) to the rsync options, a whole bunch of files got replaced, so I guess media-libs/tiff was not the only package affected. Unfortunately, "-c" slows down "emerge sync" significantly, so adding it to the default rsync options might not be an option. But ebuild files should definitely be checked for corruption (e.g. via the digest file) before using them.
I believe this is a planned feature of portage. Nothing I can do on this end, sending back to bug wranglers.
-r13 and beyond of portage use this option.