| Summary: | gdk-pixbuf ebuilds broken | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Charles N. Burns <charlesnburns> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | VERIFIED FIXED | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | 1.4_rc1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
i'd say, reinstall esound. I reinstalled esound (why should that be installed on systems without sound capabilities?) and got an error complaining about a missing file whose name contained "libz", which I assumed referred to zlib. I reinstalled zlib with the same version (?), and the gdk-pixbuf ebuild installed perfectly! Now if only I had any idea what happened with esound and zlib... Thankyou for the suggestion that put me on the path to a solution. |
gdk-pixbuf absolutely refuses to build regardless of the version. The following ebuilds generate a similar error: gdk-pixbuf/gdk-pixbuf-0.18.0-r1.ebuild gdk-pixbuf/gdk-pixbuf-0.20.0.ebuild gdk-pixbuf/gdk-pixbuf-0.21.0.ebuild As of this writing, most installed packages that depend on gdk-pixbuf wans the 0.20.0 version. When building 0.20.0, the following error occurs: --------------------------BEGIN--------------------------------- /bin/sh ../libtool --mode=link i686-pc-linux-gnu-gcc -O -pipe -o libgnomecanvaspixbuf.la -rpath /usr/lib -version-info 1:0:0 -rdynamic -L/usr/lib -L/usr/X11R6/lib -lgnomeui -lart_lgpl -lgdk_imlib -lSM -lICE -lgtk -lgdk -lgmodule -ldl -lXi -lXext -lX11 -lgnome -lgnomesupport -lesd -lasound -laudiofile -lm -ldb1 -lglib gnome-canvas-pixbuf.lo grep: /usr/lib/libesd.la: No such file or directory sed: can't read /usr/lib/libesd.la: No such file or directory libtool: link: `/usr/lib/libesd.la' is not a valid libtool archive make[3]: *** [libgnomecanvaspixbuf.la] Error 1 make[3]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.20.0/work/gdk-pixbuf-0.20.0/gdk-pixbuf' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.20.0/work/gdk-pixbuf-0.20.0/gdk-pixbuf' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gdk-pixbuf-0.20.0/work/gdk-pixbuf-0.20.0' make: *** [all-recursive-am] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line -64, Exitcode 2 !!! (no error message) ----------------------------END------------------------------ This package, unfortunately, is a dependency of several important applications, according to qpkg: media-libs/gdk-pixbuf-0.20.0 DEPENDED ON BY: app-office/dia-0.90-r1 gnome-base/control-center-1.4.0.5-r1 gnome-base/gnome-print-0.35-r3 media-gfx/gnome-iconedit-1.2.0-r5 x11-misc/xscreensaver-4.05-r3 x11-themes/gtk-engines-metal-1.9.0 I noticed the error happened to occur sometime after compiling a file whose name mentioned "MMX", so I disabled that USE flag and still no success. So, I cleared most of my USE variables and tried. Still no success. Then, I commented out the "USE=" line in make.conf to use the defaults, turned off parallel building, and set my CFLAGS to just "-O0 -pipe" using this command: FEATURES="" MAKEOPTS="-j1" CFLAGS="-O0 -pipe" emerge gdk-pixbuf I also tried with default CFLAGS, "-O -pipe" (as seen in the error), highly optimized flags, etc. Other ebuilds seem to work perfectly (well, libungif fails when using -fprefetch-loop-arrays, but no big deal). Even finicky ones like OpenOffice build fine. Possibly applicable hardware in question is: Tyan TigerMP 1GB Crucial RAM certified for this specific motherboard Adaptec 29160 SCSI controller, in 64-bit slot Maxtor Atlas 10K-III SCSI drive No sound/USB/etc, it's a minimalist server Using the Gentoo-sources kernel emerge -rsync run very recently, all configuration files properly updated My make.conf contains: #USE="X gnome gtk gtk2 -xmms -encode java perl nocardbus -cups pam ssl kde -arts -alsa" CHOST="i686-pc-linux-gnu" CFLAGS="-O -pipe" CXXFLAGS="${CFLAGS}" MAKEOPTS="-j1" AUTOCLEAN="yes" FEATURES="sandbox buildpkg" Anyone else experiencing this problem?