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
