I could be wrong, I'm very new to portage, but when I ran emerge =gcc-3.4.1-r3, and it consistentely tells me that patch 81_all_gcc-uclibc-3.4.0-100-conf-after-20040601.patch.bz2-9704.out failed to apply, I went to /var/var and checked, it IS a 3.4.0 patch, it seems that maybe someone has got their gcc-versions mixed up, I don't think these are ever going to apply. I am not enough of a gcc-programmer to figure out the use of the patch and fix it myself... I could give a close guess, but that's not good enough here, right? Reproducible: Always Steps to Reproduce: 1.emerge =gcc-3.4.1-r3 2. 3. Actual Results: chuckr@june ~ $ cat ~/emerge.out (output saved into this file-->) Calculating dependencies >>> Unpacking source... >>> Unpacking gcc-3.4.1.tar.bz2 to /var/tmp/portage/gcc-3.4.1/work >>> Unpacking gcc-3.4.1-patches-1.0.tar.bz2 to /var/tmp/portage/gcc-3.4.1/work >>> Unpacking protector-3.4-2.tar.gz to /var/tmp/portage/gcc-3.4.1/work >>> Unpacking gcc-3.4.0-piepatches-v8.7.6.3.tar.bz2 to /var/tmp/portage/gcc-3.4.1/work * Patching ${S}/ltmain.sh... * Applying portage-1.4.1.patch... * Applying relink-1.4.0a-GCC3.0-2.patch... * Applying sed-1.4.3.patch... * Applying tmp-1.3.5.patch... * Applying uClibc/libtool patches ... * Fixing ${S}/ltconfig... [ ok ] * Fixing ${S}/boehm-gc/ltconfig... [ ok ] * Applying various patches (bugfixes/updates)... * 02_all_gcc34-ice-hack.patch.bz2... [ ok ] * 16_all_gcc33-c99-double-inline.patch.bz2... [ ok ] * 22_all_gcc34-ppc64-m32-m64-multilib-only.patch.bz2... [ ok ] * 26_all_gcc33-m68k-const.patch.bz2... [ ok ] * 27_all_gcc33-m68k-java-build.patch.bz2... [ ok ] * 28_all_gcc33-m68k-loop.patch.bz2... [ ok ] * 29_all_gcc33-m68k-subreg.patch.bz2... [ ok ] * 35_all_gcc33-pr9929.patch.bz2... [ ok ] * 81_all_gcc-uclibc-3.4.0-100-conf-after-20040601.patch.bz2... * Failed Patch: 81_all_gcc-uclibc-3.4.0-100-conf-after-20040601.patch.bz2! * * Include in your bugreport the contents of: * * /var/tmp/portage/gcc-3.4.1/temp/81_all_gcc-uclibc-3.4.0-100-conf-after-20040601.patch.bz2-9704.out !!! ERROR: sys-devel/gcc-3.4.1 failed. !!! Function epatch, Line 400, Exitcode 0 !!! Failed Patch: 81_all_gcc-uclibc-3.4.0-100-conf-after-20040601.patch.bz2! !!! If you need support, post the topmost build error, NOT this status message. ...done! >>> emerge (1 of 2) sys-devel/gcc-3.4.1 to / >>> md5 src_uri ;-) gcc-3.4.1.tar.bz2 >>> md5 src_uri ;-) gcc-3.4.1-patches-1.0.tar.bz2 >>> md5 src_uri ;-) protector-3.4-2.tar.gz >>> md5 src_uri ;-) gcc-3.4.1-manpages.tar.bz2 >>> md5 src_uri ;-) gcc-3.4.0-piepatches-v8.7.6.3.tar.bz2 chuckr@june ~ $ Expected Results: Finished compiling, producing a gcc-3.4.1 compiler quite easily reproducible... pleease, I am new to gentoo bug filing, be severely critical of any error I make, so I can learn more quickly.
this bug was caused by a change in the libtool eclass. it should be fixed now
