! use xv && die ;) Submitting this on request from eradicator. configure: error: conditional "HAVE_XV" was never defined. Usually this means the macro was only invoked conditionally. When USE=xv configure completes successfully. Portage 2.0.51-r8 (default-linux/x86/2004.2, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.10 i686) ================================================================= System uname: 2.6.10 i686 AMD Athlon(tm) XP 2600+ Gentoo Base System version 1.6.8 Python: dev-lang/python-2.3.4 [2.3.4 (#1, Nov 5 2004, 12:23:37)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.4 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.3 sys-devel/binutils: 2.15.92.0.2-r2 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe" DISTDIR="/usr/local/distfiles" FEATURES="autoaddcvs autoconfig ccache collision-protect cvs digest distlocks sandbox sfperms sign strict" GENTOO_MIRRORS="ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ ftp://gentoo.chem.wisc.edu/gentoo/ ftp://mirrors.tds.net/gentoo/ ftp://ibiblio.org/pub/Linux/distributions/gentoo/" LDFLAGS="" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/ka0ttic/overlay" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X aim alsa apache2 bash-completion berkdb bzlib cdr crypt cscope doc esd fam fbcon gdbm gif gtk gtk2 imap imlib jpeg maildir mailwrapper mikmod mmx ncurses nls offensive opengl oss pam pcre pdflib perl png python readline ruby sdl slang sse ssl svga tcpd truetype unicode usb x86 xml2 xmms zlib"
*** Bug 75948 has been marked as a duplicate of this bug. ***
Ok, I've contacted upstream for clarification on the whole Xv/X11/whatever configure stuff with enabling and disabling it. I'm just waiting on a response at this point. Hopefully I'll get the mess cleared up by then :).
*** Bug 75387 has been marked as a duplicate of this bug. ***
I don't know if this helps, but... This problem only occurs if you have >xorg-x11-6.8.0-r3 compiled with USE=-xv (earlier versions of xorg don't have this use flag and so you always get libXv.*) If you have xorg-x11 installed as above, then configure fails in exactly the same way with USE=xv (unsuprising) or USE=-xv (bad) Thought I'd point that out because it's slightly different to what ka0ttic said (presumably he has libXv.* in either /usr/lib or /usr/X11R6/lib)
Created attachment 47480 [details] xine-lib-1_rc8.ebuild
Created attachment 47482 [details, diff] ebuild-rc8.patch
piolyte: does that really solve the USE=-xv problem? It looks the same (at a glance) as the xine-lib-1.0 changes but just backported to the previous ebuild. I think the problem runs deeper... maybe something in xine-lib/m4/xv.m4
Ok, I just ported the fix to 1.0 and rc8-r1. It appears it was a problem with the configure file that patching configure.ac fixes (I talked to upstream on this one :). That should be all, did test with USE="-xv" and WORKSFORME.
I'm testing it myself.
Created attachment 47559 [details] xine-lib-1.0.ebuild Works with and without USE="xv"
Created attachment 47560 [details] xine-lib-1.0.ebuild
Created attachment 47561 [details] xine-lib-1.0.ebuild these depends not found... >=sys-devel/automake-1.7 >=sys-devel/autoconf-2.59 so I let it use versions installed... sys-devel/automake sys-devel/autoconf then it finds depends
Created attachment 47580 [details, diff] xine-lib-configure.ac.patch The magical patch.
Created attachment 47581 [details] xine-lib-1_rc8-r1.ebuild
Created attachment 47582 [details] xine-lib-1_rc8-r1.ebuild
Created attachment 47583 [details] xine-lib-1_rc8-r1.ebuild
Updated xine-lib-1_rc8-r1 again, wasn't quite fixed.
*** Bug 76724 has been marked as a duplicate of this bug. ***
