* Package: dev-lang/julia-9999  * Repository: science  * Maintainer: python@gentoo.org  * USE: amd64 elibc_glibc kernel_linux userland_GNU  * FEATURES: sandbox splitdebug >>> Unpacking source... GIT update --> repository: git://github.com/JuliaLang/julia.git at the commit: 12307628dcc64de021089db1e2fd28e7f406ab40 branch: master storage directory: "/usr/portage/distfiles/egit-src/julia.git" checkout type: bare repository Cloning into '/var/tmp/portage/dev-lang/julia-9999/work/julia-9999'... done. Branch branch-master set up to track remote branch master from origin. Switched to a new branch 'branch-master' >>> Unpacked to /var/tmp/portage/dev-lang/julia-9999/work/julia-9999 >>> Source unpacked in /var/tmp/portage/dev-lang/julia-9999/work >>> Preparing source in /var/tmp/portage/dev-lang/julia-9999/work/julia-9999 ... * Applying julia-nopatchelf.patch ... * Failed Patch: julia-nopatchelf.patch ! * ( /var/lib/layman/science/dev-lang/julia/files/julia-nopatchelf.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-lang/julia-9999/temp/julia-nopatchelf.patch.out * ERROR: dev-lang/julia-9999 failed (prepare phase): * Failed Patch: julia-nopatchelf.patch! * * Call stack: * ebuild.sh, line 93: Called src_prepare * environment, line 2580: Called epatch '/var/lib/layman/science/dev-lang/julia/files/julia-nopatchelf.patch' * environment, line 1138: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * * If you need support, post the output of `emerge --info '=dev-lang/julia-9999'`, * the complete build log and the output of `emerge -pqv '=dev-lang/julia-9999'`. * This ebuild is from an overlay named 'science': '/var/lib/layman/science/' * The complete build log is located at '/var/tmp/portage/dev-lang/julia-9999/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-lang/julia-9999/temp/environment'. * Working directory: '/var/tmp/portage/dev-lang/julia-9999/work/julia-9999' * S: '/var/tmp/portage/dev-lang/julia-9999/work/julia-9999'