| 1 |
On 06/10/14 00:05, walt wrote: |
| 2 |
> On 10/04/2014 09:15 PM, Bruce Schultz wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> I'm trying to update a system using binary packages build on another system. I get this error for glibc: |
| 6 |
>> |
| 7 |
>> >>> Emerging binary (1 of 1) sys-libs/glibc-2.19-r1::gentoo |
| 8 |
>> * glibc-2.19-r1.tbz2 MD5 SHA1 size ;-) ... [ ok ] |
| 9 |
>> >>> Extracting info |
| 10 |
>> |
| 11 |
>> >>> Failed to emerge sys-libs/glibc-2.19-r1, Log file: |
| 12 |
>> |
| 13 |
>> >>> '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/build.log' |
| 14 |
>> |
| 15 |
>> * Messages for package sys-libs/glibc-2.19-r1: |
| 16 |
>> |
| 17 |
>> * ERROR: sys-libs/glibc-2.19-r1::gentoo failed (setup phase): |
| 18 |
>> * nonfatal() not supported in this EAPI |
| 19 |
>> * |
| 20 |
>> * Call stack: |
| 21 |
>> * ebuild.sh, line 93: Called pkg_setup |
| 22 |
>> * environment, line 2870: Called eblit-run 'pkg_setup' |
| 23 |
>> * environment, line 987: Called eblit-glibc-pkg_setup |
| 24 |
>> * environment, line 843: Called glibc_run_test '#include <pwd.h> |
| 25 |
>> * int main(){return getpwuid(0)==0;} |
| 26 |
>> * ' |
| 27 |
>> * environment, line 2085: Called glibc_compile_test '' '#include <pwd.h> |
| 28 |
>> * int main(){return getpwuid(0)==0;} |
| 29 |
>> * ' |
| 30 |
>> * environment, line 1998: Called nonfatal 'emake' '-s' 'glibc-test' |
| 31 |
>> * isolated-functions.sh, line 92: Called die |
| 32 |
>> * The specific snippet of code: |
| 33 |
>> * |
| 34 |
> die "$FUNCNAME() not supported in this EAPI" |
| 35 |
> |
| 36 |
> I have isolated-functions.sh in two places: |
| 37 |
> |
| 38 |
> /usr/lib64/portage/python2.7/isolated-functions.sh |
| 39 |
> /usr/lib64/portage/python3.3/isolated-functions.sh |
| 40 |
> but not in /usr/lib64/portage/python3.4 (which I didn't know was installed til now) |
| 41 |
> |
| 42 |
> You might want to check the target machine for which version of python it's using |
| 43 |
> and that it has the latest version of portage in /usr/lib/portage/pythonN.N/ |
| 44 |
> |
| 45 |
> Maybe running python-updater would help? |
| 46 |
> |
| 47 |
> |
| 48 |
Tried switching to python 2.7 but got the same error. |
| 49 |
|
| 50 |
The line of the error in isolated-functions.sh is calling a function |
| 51 |
__eapi_has_nonfatal. That is defined in eapi.sh and checks if ${EAPI} != |
| 52 |
0, 1, 2 or 3, which effectively leave 4 or 5. |
| 53 |
|
| 54 |
It seems that the glibc ebuild is EAPI 0 (from |
| 55 |
/var/db/pkg/sys-libs/glibc-2.19-r1/EAPI). |
| 56 |
|
| 57 |
So I guess that the error means that it tried to run the |
| 58 |
glibc_compile_test and failed for the binary install, so emerge tried to |
| 59 |
raise a nonfatal error, but that wasn't supported by the EAPI and that |
| 60 |
caused the emerge to die. |
| 61 |
|
| 62 |
I wonder if setting EAPI=5 in the ebuild file will help, of if that |
| 63 |
would just cause other problems... I might try that later when I have |
| 64 |
some time... |
| 65 |
|
| 66 |
:B |
Archives