I am not sure if this is a ebuild problem or even a GENTOO problem. Anyway, the ebuild maintainers could fix the problem. Problem: LINGUAS=pt_PT -> kde-i18n do not install the portuguese version! LINGUAS=pt -> Compiling (building?) bintuils fails! This seems to be the relevant line make[3]: *** No rule to make target `pt.gmo', needed by `all-yes'. Stop. See below the output ... At least one of these packages should be fixed. I don't know what is the behaviour of other applications. As a turnaround, I am using LINGUAS=pt and change it to pt_PT to emerge binutils. Other applications compile fine but I am not sure if all of them generate the appropriate nls for standard european portuguese when available. __________________________________________________________________ ... (cd .libs && rm -f libbfd.la && ln -s ../libbfd.la libbfd.la) libtooldir=`/bin/sh ./libtool --config | sed -n -e 's/^objdir=//p'`; \ if [ -f $libtooldir/libbfd.a ]; then \ cp $libtooldir/libbfd.a libbfd.tmp; \ i686-pc-linux-gnu-ranlib libbfd.tmp; \ /bin/sh /var/tmp/portage/binutils-2.16.1-r3/work/binutils-2.16.1/bfd/../move-if-change libbfd.tmp libbfd.a; \ else true; fi touch stamp-lib make[3]: Leaving directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/bfd' make[2]: Leaving directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/bfd' make[1]: Leaving directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/bfd' make[1]: Entering directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/opcodes' make all-recursive make[2]: Entering directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/opcodes' Making all in po make[3]: Entering directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/opcodes/po' make[3]: *** No rule to make target `pt.gmo', needed by `all-yes'. Stop. make[3]: Leaving directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/opcodes/po' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/opcodes' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/binutils-2.16.1-r3/work/build/opcodes' make: *** [all-opcodes] Error 2 !!! ERROR: sys-devel/binutils-2.16.1-r3 failed. Call stack: ebuild.sh, line 1539: Called dyn_compile ebuild.sh, line 939: Called src_compile ebuild.sh, line 1248: Called toolchain-binutils_src_compile toolchain-binutils.eclass, line 191: Called die !!! emake failed !!! If you need support, post the topmost build error, and the call stack if relevant.
ignoring the fact you forgot to post `emerge info`, this works fine for me in fact, you should see this warning: * Sorry, but binutils does not support the LINGUAs: pt run `emerge binutils >& log` and post the log as an attachment
Created attachment 91584 [details] emerge binutils log
Created attachment 91586 [details] emerge einfo
Created attachment 91587 [details] emerge einfo
Because I am not sure the previous attachements I sent were properly obtained (I made a few tests with LINGUAS), I reproduced the whole situation from scratch. The problem remains as first reported. I'll create new attachments for emerge info and emerge binutils.
Created attachment 91711 [details] emerge --info
Created attachment 91712 [details] emerge binutils log
you could try moving the `strip-linguas` in toolchain-binutils.eclass from the end of src_unpack to the top of src_compile and see if that helps at all
(In reply to comment #8) > you could try moving the `strip-linguas` in toolchain-binutils.eclass from the > end of src_unpack to the top of src_compile and see if that helps at all > I moved the lines as follows, and *yes*, it *does* work! Now? Do I have to change this every "emerge --sync"? ______________________________________________________ toolchain-binutils_src_compile() { strip-flags && replace-flags -O3 -O2 #47581 # make sure we filter $LINGUAS so that only ones that # actually work make it through #42033 strip-linguas -u */po local x ...
fixed in cvs then
