The ppc patch 3.7.11-ppc-configure.patch has an error and wan't be applied. As commenting out of this patch shown the package compiles on x86 processor without any problem. P.S. gcc4.1.1 >>> Emerging (4 of 7) sci-libs/blas-atlas-3.7.11-r1 to / >>> Creating Manifest for /portage/portage/sci-libs/blas-atlas digest.assumed 3 digest-blas-atlas-3.6.0::atlas3.6.0-shared-libs.patch.bz2 digest-blas-atlas-3.6.0::atlas3.6.0.tar.bz2 digest-blas-atlas-3.6.0-r1::atlas3.6.0.tar.bz2 digest-blas-atlas-3.6.0-r2::atlas3.6.0.tar.bz2 digest-blas-atlas-3.7.10::atlas3.6.0-shared-libs.patch.bz2 digest-blas-atlas-3.7.10::atlas3.7.10.tar.bz2 * You need one of these Fortran Compilers: g77 gfortran * Installed are: gfortran >>> Unpacking source... >>> Unpacking atlas3.7.11.tar.bz2 to /portage/tmp/portage/blas-atlas-3.7.11-r1/work >>> Unpacking atlas3.6.0-shared-libs.1.patch.bz2 to /portage/tmp/portage/blas-atlas-3.7.11-r1/work * Applying unbuffered.patch ... [ ok ] * Applying 3.7.11-allow-any-gcc-version.patch ... [ ok ] * Applying atlas3.6.0-shared-libs.1.patch.bz2 ... [ ok ] * Applying 3.7.11-ppc-configure.patch ... * Failed Patch: 3.7.11-ppc-configure.patch ! * ( /portage/portage/sci-libs/blas-atlas/files/3.7.11-ppc-configure.patch ) * * Include in your bugreport the contents of: * * /portage/tmp/portage/blas-atlas-3.7.11-r1/temp/3.7.11-ppc-configure.patch-15483.out !!! ERROR: sci-libs/blas-atlas-3.7.11-r1 failed. Call stack: ebuild.sh, line 1545: Called dyn_unpack ebuild.sh, line 711: Called src_unpack blas-atlas-3.7.11-r1.ebuild, line 37: Called epatch '/portage/portage/sci-libs/blas-atlas/files/3.7.11-ppc-configure.patch' eutils.eclass, line 335: Called die
Did you read this part? * Failed Patch: 3.7.11-ppc-configure.patch ! * ( /portage/portage/sci-libs/blas-atlas/files/3.7.11-ppc-configure.patch ) * * Include in your bugreport the contents of: * * /portage/tmp/portage/blas-atlas-3.7.11-r1/temp/3.7.11-ppc-configure.patch-15483.out
Hi Alexey, I believe I fixed this very issue yesterday for 3.7.11-r1. Please resync and try again and report back how it goes. Thanks, Markus
> I believe I fixed this very issue yesterday for 3.7.11-r1. Please > resync and try again and report back how it goes. Yes. It works now. Thanks a lot!!! We may close this bug.
