Emerge of mplayer-1.0_pre4 fails with the following message: install: cannot stat `DOCS/man/_GB/mplayer.1': No such file or directory make: *** [install] Error 1 !!! ERROR: media-video/mplayer-1.0_pre4 failed. !!! Function src_install, Line 284, Exitcode 2 !!! Failed to install MPlayer! My USE flags are: antlr autofs dvd flash java jdepend jython mmx moznocompose moznoirc \ moznomail odbc pcmcia pda pic ppds samba sse tiff usb -gnome -gtk \ -ldap Reproducible: Always Steps to Reproduce: 1. With the emerge flags shown in details section. 2. emerge -auv mplayer 3. Actual Results: See details section. Expected Results: emerged successfully No other programs running. Using KDE 3.2.1. Tried with the gtk flag and without.
Had the same problem... worked around by commenting out my LINGUAS="en en_gb" line in make.conf.
Thanks for that. I tried LINGUAS="en" instead of LINGUAS="en en_GB en_US" and it compiled fine.
Verified it, thoughts/preferences on how to deal with it? Bit busy at the moment so this isn't top priority, added, I have no freaking clue about linguas support, so advice would be welcome :)
I've added some bash logic to make things more simplistic regarding MPlayer's parsing of linguas in a format some people may not be used to. For example, I have a perfectly ok locale setup in LINGUAS, ja_JP. However, when MPlayer looks for the locale information, it looks for a file ${S}/help/help_mp-ja.h for example, but this will make it look for ${S}/help/help_mp-ja_JP.h, which isn't going to work out :). Therefore, the ebuild will now do this in the following situations: 1) Your locale is a valid locale, ja_JP for example, but MPlayer only wants ja. This'll do it for you!: * Setting MPlayer messages to language ja Checking for language ... using ja (man pages: en) Hey alright! It's strips the _JP for you to give you a perfectly valid LINGUAS variable for MPlayer to work with! Now, if you have ja as your first LINGUAS, the ebuild will see that too and detect it right away before it does illegal character stripping! 2) MPlayer has no clue what your locale is aa_BB or aa. We default it to english so no more weirdness! * Language aa_BB or aa not avaliable * Language set to English * If this is a mistake, please set the * First LINGUAS language to one of the following * * bg - Bulgarian * cz - Czech * de - German * dk - Swedish * el - Greek * en - English * es - Spanish * fr - French * hu - Hungarian * ja - Japanese * ko - Korean * mk - FYRO Macedonian * nl - Dutch * no - Norwegian * pl - Polish * pt_BR - Portuguese - Brazil * ro - Romanian * ru - Russian * sk - Slovak * tr - Turkish * uk - Ukranian * zh_CN - Chinese - China * zh_TW - Chinese - Taiwan Checking for language ... using en (man pages: en) Just in case you made a mistake or something, it even gives you what to set to LINGUAS for different languages! 3) Your first LINGUAS is a instead of aa_BB. Normally if it was parsed, you'd get a nice blargy warning from bash, but oh no, I checked that one too :P. So there.. now the LINGUAS stuff will make more sense (I hope) and not give people so much of a headache :P. in CVS!
