From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-58169-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 8AF74138821
	for <garchives@archives.gentoo.org>; Sun,  3 Feb 2013 11:08:34 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id DC9BA21C02A;
	Sun,  3 Feb 2013 11:08:32 +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 D035A21C020
	for <gentoo-dev@lists.gentoo.org>; Sun,  3 Feb 2013 11:08:31 +0000 (UTC)
Received: from proton.in.awa.tohoku.ac.jp (softbank126006199115.bbtec.net [126.6.199.115])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: heroxbd)
	by smtp.gentoo.org (Postfix) with ESMTPSA id 2490533DD79
	for <gentoo-dev@lists.gentoo.org>; Sun,  3 Feb 2013 11:08:29 +0000 (UTC)
From: heroxbd <heroxbd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] meaning of EROOT
Date: Sun, 03 Feb 2013 20:07:21 +0900
Message-ID: <87wqupsljq.fsf@proton.in.awa.tohoku.ac.jp>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain
X-Archives-Salt: c55f6438-7a9e-49d8-8a76-9f0856b953f9
X-Archives-Hash: eb62d000adb5e8a07dfd1e7073a4cb68

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?

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?

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.

Cheers,
Benda