This is for media-video/mplayer-1.0_pre7-r1. In emerging this version (again and again), the configure is not picking up that /usr/lib/win32 is a directory (it is, and win32codecs is emerged also). So, the end result for Win32 codec DLL support is no. Reproducible: Always Steps to Reproduce: 1. emerge win32codecs 2. emerge mplayer Actual Results: When trying to use mplayer to view a file with a win32 codec, it complains: Requested video codec family [wmv9dmo] (vfm=dmo) not available. Enable it at compilation. Requested video codec family [wmvdmo] (vfm=dmo) not available. Enable it at compilation. Cannot find codec matching selected -vo and video format 0x33564D57. Read DOCS/HTML/en/codecs.html! Expected Results: It should have found the codec and played the file. Portage 2.0.51.22-r2 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r1, 2.6.13 i686) ================================================================= System uname: 2.6.13 i686 Pentium III (Coppermine) Gentoo Base System version 1.12.0_pre8 dev-lang/python: 2.2.3-r5, 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.12 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 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=pentium3 -O3 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo http://prometheus.cs.wmich.edu/gentoo http://gentoo.mirrors.tds.net/gentoo http://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 X acpi alsa apache2 apm avi berkdb bitmap-fonts bonobo cdr crypt cscope cups curl dba divx4linux doc dvb dvd dvdr dvdread eds emboss encode esd exif fam flac foomaticdb fortran gd gdbm gif gnome gpm gstreamer gtk gtk2 gtkhtml guile imagemagick imlib ipv6 jack java jpeg junit kde ldap libg++ libwww mad mikmod mmx motif mozilla mp3 mpeg mysql ncurses nls nptl nvidia ogg oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba scanner sdl slang spell sse ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts usb vorbis xine xml xml2 xmms xv xvid zeroconf zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Is mplayer win32codecs flag enabled?
I thought this would automatically be enabled if win32codecs is installed. This is what I'm debugging now.
Well, I added a 'media-video/mplayer win32codecs' to /etc/portage/package.use and it looks like mplayer is building with win32 codec support now. Shouldn't this have been taken care of by the RDEPEND?
Ah... ok, I see now. In /usr/portage/profiles/default-linux/x86/use.mask is a -win32codecs line. Am I right - is this what caused my problem (other than my lack of knowledge about portage)? Why is this in use.mask?
Can't seem to stop... ok, last comment. profiles/default-linux/use.mask has win32codecs. profiles/default-linux/x86/use.mask has -win32codecs. Isn't this backwards? It seems to me that if you have a ppc, you don't want win32codecs on by default but you may when using x86.... ??
really the last comment... ok, use.mask. The win32codecs in default-linux/use.mask makes sense. It *masks* win32codecs. And the -win32codecs in default-linux/x86/use.mask makes sense. It *un-masks* the masking of win32codecs in default-linux/use.mask. Correct? Then how come when I emerge mplayer, I need a win32codecs in my /etc/portage/package.use? I'm just trying to learn, honest...
That a use flag is not masked on a particular architecture doesn't mean it is enabled by default.