From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-159135-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 5A8EA13838B
	for <garchives@archives.gentoo.org>; Mon,  6 Oct 2014 02:44:43 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 26ED5E0AA4;
	Mon,  6 Oct 2014 02:44:35 +0000 (UTC)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id E2236E0A04
	for <gentoo-user@lists.gentoo.org>; Mon,  6 Oct 2014 02:44:33 +0000 (UTC)
Received: by mail-pd0-f172.google.com with SMTP id ft15so2572371pdb.3
        for <gentoo-user@lists.gentoo.org>; Sun, 05 Oct 2014 19:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=5XrIm33tZPUvCgiBNZhj+PRO/xCfsT7hGuAk2wDapYk=;
        b=OlB/epSUb9CJoSaVqZjFzZG3RhdH0x3YgutmkVD1JsqVWQSEk6vANiSJiVP7oWX+Ny
         FkYG+JZDOPy2Nxv2sClHl28Zn2RAj9JGwwTygSVoAwBTMYn9VOE4Tsf33nZ6G7gBgWbR
         4lEcTQChoPQdHR4pZ0CAC48QqqbwhgmkloWmHYovNt1JhHvBoOHZc+RIigOH+flHD2FC
         g3n+sagI4BZ96YfFDqEVrx9d+HrWvGbipmwlcz6mpjR8sL4J3tLxAuScenA+53LC+GX6
         VNWsF76n44TnG7+Y6d4AnH1sRLpQKv26obQeTyC+A+6wMX9pb6NF02ZcLWqx6DAPoUkW
         61SA==
X-Received: by 10.66.192.232 with SMTP id hj8mr468096pac.117.1412563472801;
        Sun, 05 Oct 2014 19:44:32 -0700 (PDT)
Received: from [192.168.1.89] (16.86.70.115.static.exetel.com.au. [115.70.86.16])
        by mx.google.com with ESMTPSA id pb1sm9636390pdb.74.2014.10.05.19.44.30
        for <gentoo-user@lists.gentoo.org>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sun, 05 Oct 2014 19:44:31 -0700 (PDT)
Message-ID: <543200B5.8000107@gmail.com>
Date: Mon, 06 Oct 2014 12:38:45 +1000
From: Bruce Schultz <brulzki@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: nonfatal() not supported error in glibc binary
 install
References: <5430C5CF.5030504@gmail.com> <m0rj7g$sio$1@ger.gmane.org>
In-Reply-To: <m0rj7g$sio$1@ger.gmane.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 7680ab9c-16ca-457c-8127-98b6de00c5d3
X-Archives-Hash: 74ba61c77229c626b00f2ee2afc0b7bb

On 06/10/14 00:05, walt wrote:
> On 10/04/2014 09:15 PM, Bruce Schultz wrote:
>> Hi,
>>
>> I'm trying to update a system using binary packages build on another system. I get this error for glibc:
>>
>>   >>> Emerging binary (1 of 1) sys-libs/glibc-2.19-r1::gentoo
>>   * glibc-2.19-r1.tbz2 MD5 SHA1 size ;-) ...                              [ ok ]
>>   >>> Extracting info
>>
>>   >>> Failed to emerge sys-libs/glibc-2.19-r1, Log file:
>>
>>   >>> '/var/tmp/portage/sys-libs/glibc-2.19-r1/temp/build.log'
>>
>>   * Messages for package sys-libs/glibc-2.19-r1:
>>
>>   * ERROR: sys-libs/glibc-2.19-r1::gentoo failed (setup phase):
>>   *   nonfatal() not supported in this EAPI
>>   *
>>   * Call stack:
>>   *               ebuild.sh, line   93:  Called pkg_setup
>>   *             environment, line 2870:  Called eblit-run 'pkg_setup'
>>   *             environment, line  987:  Called eblit-glibc-pkg_setup
>>   *             environment, line  843:  Called glibc_run_test '#include <pwd.h>
>>   * int main(){return getpwuid(0)==0;}
>>   * '
>>   *             environment, line 2085:  Called glibc_compile_test '' '#include <pwd.h>
>>   * int main(){return getpwuid(0)==0;}
>>   * '
>>   *             environment, line 1998:  Called nonfatal 'emake' '-s' 'glibc-test'
>>   *   isolated-functions.sh, line   92:  Called die
>>   * The specific snippet of code:
>>   *
>            die "$FUNCNAME() not supported in this EAPI"
>
> I have isolated-functions.sh in two places:
>
> /usr/lib64/portage/python2.7/isolated-functions.sh
> /usr/lib64/portage/python3.3/isolated-functions.sh
> but not in /usr/lib64/portage/python3.4 (which I didn't know was installed til now)
>
> You might want to check the target machine for which version of python it's using
> and that it has the latest version of portage in /usr/lib/portage/pythonN.N/
>
> Maybe running python-updater would help?
>
>
Tried switching to python 2.7 but got the same error.

The line of the error in isolated-functions.sh is calling a function 
__eapi_has_nonfatal. That is defined in eapi.sh and checks if ${EAPI} != 
0, 1, 2 or 3, which effectively leave 4 or 5.

It seems that the glibc ebuild is EAPI 0 (from 
/var/db/pkg/sys-libs/glibc-2.19-r1/EAPI).

So I guess that the error means that it tried to run the 
glibc_compile_test and failed for the binary install, so emerge tried to 
raise a nonfatal error, but that wasn't supported by the EAPI and that 
caused the emerge to die.

I wonder if setting EAPI=5 in the ebuild file will help, of if that 
would just cause other problems... I might try that later when I have 
some time...

:B