From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] meaning of EROOT
Date: Sun, 03 Feb 2013 12:56:29 -0800 [thread overview]
Message-ID: <510ECEFD.8060405@gentoo.org> (raw)
In-Reply-To: <87wqupsljq.fsf@proton.in.awa.tohoku.ac.jp>
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
next prev parent reply other threads:[~2013-02-03 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 11:07 [gentoo-dev] meaning of EROOT heroxbd
2013-02-03 20:56 ` Zac Medico [this message]
2013-02-04 11:01 ` Michael Weber
2013-02-04 16:07 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=510ECEFD.8060405@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox