Emerging alsa-lib and/or alsa-jack 1.0.6 gives a warning when applying a patch. The patch appears to be missing. Emerge *will* continue to compile and install the unpatched programs. Reproducible: Always Steps to Reproduce: USE="jack -static" emerge -av =alsa-lib-1.0.6 =alsa-jack-1.0.6 Actual Results: >>> emerge (1 of 2) media-libs/alsa-lib-1.0.6 to / >>> md5 src_uri ;-) alsa-lib-1.0.6.tar.bz2 >>> Unpacking source... >>> Unpacking alsa-lib-1.0.6.tar.bz2 to /var/tmp/portage/alsa-lib-1.0.6/work * Patching ${S}/ltmain.sh... * Applying portage-1.4.1.patch... * Applying max_cmd_len-1.5.0.patch... * Applying sed-1.4.3.patch... * Applying uClibc/libtool patches ... * Fixing ${S}/ltconfig... patch: **** Can't open patch file /usr/portage/eclass/ELT-patches/uclibc/ ltconfig-.patch : No such file or directory * PLEASE CHECK /var/tmp/portage/alsa-lib-1.0.6/work/alsa-lib-1.0.6/ltco [ !! ] >>> Source unpacked. Emerge then continues to compile and install alsa-lib, apparently successfully. The problem with alsa-jack is identical. The file mentioned in the 'PLEASE CHECK' does not exist. Expected Results: No 'PLEASE CHECK' warning. Portage 2.0.50-r11 (default-x86-1.4, gcc-3.3.4, glibc-2.3.3.20040420-r1, 2.6.8- gentoo-r3) ================================================================= System uname: 2.6.8-gentoo-r3 i686 Mobile Intel(R) Celeron(R) CPU 1.80GHz Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=i686 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/ share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="ftp://ftp.heanet.ie/pub/gentoo/ http://mirrors.sec.informatik. tu-darmstadt.de/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" USE="X aalib alsa apm avi berkdb bitmap-fonts crypt cups dga divx4linux fbcon foomaticdb gdbm gif gpm gtk gtk2 guile jack jack-tmpfs java jikes jpeg libcaca libg++ libwww mad mikmod mmx mng motif mpeg ncurses nls oggvorbis opengl pam pcmcia pdflib perl png pnp python qt quicktime readline ruby sdl slang spell sse ssl svg svga tcltk tcpd tiff truetype unicode usb wmf x86 xml xml2 xmms xprint xv xvid zlib"
same here, and I find it worying that portage goes on!
this isn't an alsa-* problem... it's a problem with the libtool eclass it looks like... try doing an 'emerge --sync' and trying again...
Just synced, error/warning still remains!
Same error with portage 2.0.51-rc6 and alsa-lib-1.0.5-r3 (which is stable at the moment)
Just to add a comment on this: the portage should really not continue to compile, if patching fails. I don't know how the convention is, but either the ebuilds should do "elibtoolize || die" instead of just "elibtoolize", or the elibtoolize should terminate the build-process on its own by calling die or exit.
Hi all, I ran across the same problem and think it'd effecting xmms. Today, after re-synching and doing an emerge -uD world, portage wanted to downgrade me from alsa-lib 1.06 to 1.05-r3. In addition, when it emerged this, I got the previously described problem and more (see below). Something is clearly amiss here. Alex Calculating world dependencies ...done! >>> emerge (1 of 1) media-libs/alsa-lib-1.0.5-r3 to / >>> md5 src_uri ;-) alsa-lib-1.0.5.tar.bz2 >>> Unpacking source... >>> Unpacking alsa-lib-1.0.5.tar.bz2 to /var/tmp/portage/alsa-lib-1.0.5-r3/work * Patching ${S}/ltmain.sh... * Applying portage-1.4.1.patch... * Could not apply relink.patch! * Applying sed-1.4.3.patch... * Applying test-1.4.1.patch... * Applying tmp-1.3.5.patch... * Applying uClibc/libtool patches ... * Fixing ${S}/ltconfig... patch: **** Can't open patch file /usr/portage/eclass/ELT-patches/uclibc/ltconfig-.patch : No such file or directory * PLEASE CHECK /var/tmp/portage/alsa-lib-1.0.5-r3/work/alsa-lib-1.0.5/l [ !! ]
dunno what the deal is here... but the libtool eclass is vapier's territory...
it's a warning that can be ignored, it'll only affect uclibc environments (which none of you use)
ok, for some weird reason, alsa-lib and xmms have a 0 byte ltconfig file added some code to ignore ltconfig files when byte size == 0
