From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2112D138833 for ; Sun, 3 Feb 2013 20:56:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DB6CF21C0A1; Sun, 3 Feb 2013 20:56:41 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id D1E3C21C09E for ; Sun, 3 Feb 2013 20:56:40 +0000 (UTC) Received: from [192.168.26.5] (ip98-164-195-43.oc.oc.cox.net [98.164.195.43]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 0763933DD9F for ; Sun, 3 Feb 2013 20:56:29 +0000 (UTC) Message-ID: <510ECEFD.8060405@gentoo.org> Date: Sun, 03 Feb 2013 12:56:29 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130112 Thunderbird/17.0.2 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] meaning of EROOT References: <87wqupsljq.fsf@proton.in.awa.tohoku.ac.jp> In-Reply-To: <87wqupsljq.fsf@proton.in.awa.tohoku.ac.jp> X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: cc66468d-a375-4b9e-8668-21e2f2ff85c8 X-Archives-Hash: 30e08a406c3d155dcd114e5cbcb89968 On 02/03/2013 03:07 AM, heroxbd wrote: > Dear All, > > I am a bit confused with the meaning of EROOT. > > In a usual Prefix installation, ROOT=/ and EPREFIX=/opt/gentoo, > EROOT=/opt/gentoo/. > > Naturally, EROOT=${EPREFIX}${ROOT}, right? No, it's EROOT=${ROOT%/}${EPREFIX}/ > But for example in ./python.eclass > > EROOT="${ROOT%/}${EPREFIX}/" > > and in LocationsManager.py of portage > > self.eroot = self.target_root.rstrip(os.sep) + self.eprefix + os.sep > > What is the logic behind this construction? ROOT corresponds to a valid chroot point. EPREFIX is an offset inside a valid chroot point. > The problem rises when I want to cross-compile under Prefix. Taking > armv7a-hardfloat-linux-gnueabi for example, > ROOT=/usr/armv7a-hardfloat-linux-gnueabi/, EPREFIX=/opt/gentoo. I'd > expect EROOT to be ${EPREFIX}${ROOT}, therefore, > /opt/gentoo/usr/armv7a-hardfloat-linux-gnueabi/. At present > EROOT=/usr/armv7a-hardfloat-linux-gnueabi/opt/gentoo/, which is > completely useless. You've filed this bug on the same topic: https://bugs.gentoo.org/show_bug.cgi?id=395633 We should continue there. -- Thanks, Zac