>>> Unpacking gutenprint-5.0.0-rc2-m4.patch.bz2 to /var/tmp/portage/gimp-print-5.0.0_rc2/work * Applying gutenprint-5.0.0-rc2-asneeded.patch ... [ ok ] * Applying gutenprint-5.0.0-rc2-m4.patch ... [ ok ] * Running eautoreconf in '/var/tmp/portage/gimp-print-5.0.0_rc2/work/gutenprint-5.0.0-rc2' ... * Running aclocal -I m4extra -I m4 ... [ ok ] * Running libtoolize --copy --force --automake ... [ ok ] * Running aclocal -I m4extra -I m4 ... [ ok ] * Running autoconf ... [ !! ] * Failed Running autoconf ! * * Include in your bugreport the contents of: * * /var/tmp/portage/gimp-print-5.0.0_rc2/temp/autoconf-17228.out !!! ERROR: media-gfx/gimp-print-5.0.0_rc2 failed. Call stack: ebuild.sh, line 1933: Called dyn_unpack ebuild.sh, line 719: Called src_unpack gimp-print-5.0.0_rc2.ebuild, line 51: Called eautoreconf autotools.eclass, line 66: Called eautoconf autotools.eclass, line 137: Called autotools_run_tool 'unpack' # cat /var/tmp/portage/gimp-print-5.0.0_rc2/temp/autoconf-17228.out ***** autoconf ***** configure:27299: error: possibly undefined macro: AM_PATH_GLIB If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. # emerge --info Portage 2.1_pre5-r3 (default-linux/x86/2005.1, gcc-3.4.5, glibc-2.3.6-r3, 2.6.14-gentoo-r5 i686) ================================================================= System uname: 2.6.14-gentoo-r5 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.12.0_pre16 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.4 [enabled] dev-lang/python: 2.4.2-r1 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -march=i686 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -march=i686 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache confcache distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.inode.at" LANG="it_IT.UTF8" LDFLAGS="-Wl,-O1,--sort-common,--no-keep-memory -s" LINGUAS="it" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X aac acpi alsa amr apache2 asf bash-completion berkdb bzip2 ccache cdrom clamav clamd courier cracklib crypt css cups dbus dio dlloader dmx dri firefox fontconfig foomaticdb ftp gd gd-external gdbm gif gimpprint gpm gs hal imlib java javascript jpeg libwww live mad mmx mmxext mp3 mpeg mplayer musepack mysql ncurses nls nptl nptlonly nsplugin ogg oggvorbis opengl oss pam pcre pdf php png ppds quicktime readline real reiserfs rtc samba session spell ssl svg tcpd theora timidity truetype truetype-fonts type1-fonts unicode usb userlocales utf8 vhosts vorbis win32codecs wma xine xml xv zip zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux linguas_it userland_GNU video_cards_trident" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LC_ALL
Excuse me if I didn't introduce the bug :D I just forgot... Bye ;)
Are you sure you have synced recently?
I've synced 1 hour ago...
I am having the exact same problem on my server which does not have X or glib installed. On my other computers, gimp-print installs fine. Here's my output of emerge info: Portage 2.0.54 (default-linux/x86/2005.0, gcc-3.4.5, glibc-2.3.5-r2, 2 too-r10 i686) ================================================================= System uname: 2.6.12-gentoo-r10 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.6.14 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632 ed] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config / /config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.gg3.net/ http://ftp.isu.edu.tw/pub/Linux ttp://gentoo.kems.net http://gentoo.channelx.biz/" MAKEOPTS="-j2" PKGDIR="/var/tmp/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/public/overlays" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 acl apache2 apm berkdb bitmap-fonts bzip2 cdr cli crypt cups eds emboss encode expat foomaticdb fortran gcj gdbm gif gpm gstreamer ck imlib ipv6 java jpeg jpg lcms ldap libg++ libwww mad maildir mhash 3 mpeg mysql ncurses nls nowin ogg oggvorbis openssl pam pcre pdflib p hp5 png ppds python quicktime readline samba sasl scanner session simp ll ssl tcpd tiff truetype-fonts type1-fonts udev usb vorbis xml xml2 x ib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
This problem is caused by the m4 patches being applied as specified in the ebuild. If I comment out the m4 patches, gimp-print installs successfully on my system. In the ebuild, in the src_unpack function, I used the following: src_unpack() { unpack ${A} cd ${S} epatch "${FILESDIR}/${MY_P}-asneeded.patch" # epatch "${WORKDIR}/${MY_P}-m4.patch" # Remove the broken libtool.m4 # rm ${S}/m4extra/libtool.m4 # AT_M4DIR="m4 m4extra" eautoreconf } With these changes, it compiles and installs fine. I don't know what these patches are doing, but they are definitely making incorrect assumptions about what is installed on my system (glib!!).
Okay I found the problem, unfortunately epatch is not an AI and when the patch applies at -p0 it's applied so without considering that files _might_ go in the wrong place. I've added a little workaround that won't require a new patch to be rolled out, and works fine.
