1 |
On 10/04/2014 09:15 PM, Bruce Schultz wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I'm trying to update a system using binary packages build on another system. I get this error for glibc: |
5 |
> |
6 |
> >>> Emerging binary (1 of 1) sys-libs/glibc-2.19-r1::gentoo |
7 |
> * glibc-2.19-r1.tbz2 MD5 SHA1 size ;-) ... [ ok ] |
8 |
> >>> Extracting info |
9 |
> |
10 |
> >>> Failed to emerge sys-libs/glibc-2.19-r1, Log file: |
11 |
> |
12 |
> >>> '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/build.log' |
13 |
> |
14 |
> * Messages for package sys-libs/glibc-2.19-r1: |
15 |
> |
16 |
> * ERROR: sys-libs/glibc-2.19-r1::gentoo failed (setup phase): |
17 |
> * nonfatal() not supported in this EAPI |
18 |
> * |
19 |
> * Call stack: |
20 |
> * ebuild.sh, line 93: Called pkg_setup |
21 |
> * environment, line 2870: Called eblit-run 'pkg_setup' |
22 |
> * environment, line 987: Called eblit-glibc-pkg_setup |
23 |
> * environment, line 843: Called glibc_run_test '#include <pwd.h> |
24 |
> * int main(){return getpwuid(0)==0;} |
25 |
> * ' |
26 |
> * environment, line 2085: Called glibc_compile_test '' '#include <pwd.h> |
27 |
> * int main(){return getpwuid(0)==0;} |
28 |
> * ' |
29 |
> * environment, line 1998: Called nonfatal 'emake' '-s' 'glibc-test' |
30 |
> * isolated-functions.sh, line 92: Called die |
31 |
> * The specific snippet of code: |
32 |
> * |
33 |
die "$FUNCNAME() not supported in this EAPI" |
34 |
|
35 |
I have isolated-functions.sh in two places: |
36 |
|
37 |
/usr/lib64/portage/python2.7/isolated-functions.sh |
38 |
/usr/lib64/portage/python3.3/isolated-functions.sh |
39 |
but not in /usr/lib64/portage/python3.4 (which I didn't know was installed til now) |
40 |
|
41 |
You might want to check the target machine for which version of python it's using |
42 |
and that it has the latest version of portage in /usr/lib/portage/pythonN.N/ |
43 |
|
44 |
Maybe running python-updater would help? |