1 |
Dear All, |
2 |
|
3 |
I am a bit confused with the meaning of EROOT. |
4 |
|
5 |
In a usual Prefix installation, ROOT=/ and EPREFIX=/opt/gentoo, |
6 |
EROOT=/opt/gentoo/. |
7 |
|
8 |
Naturally, EROOT=${EPREFIX}${ROOT}, right? |
9 |
|
10 |
But for example in ./python.eclass |
11 |
|
12 |
EROOT="${ROOT%/}${EPREFIX}/" |
13 |
|
14 |
and in LocationsManager.py of portage |
15 |
|
16 |
self.eroot = self.target_root.rstrip(os.sep) + self.eprefix + os.sep |
17 |
|
18 |
What is the logic behind this construction? |
19 |
|
20 |
The problem rises when I want to cross-compile under Prefix. Taking |
21 |
armv7a-hardfloat-linux-gnueabi for example, |
22 |
ROOT=/usr/armv7a-hardfloat-linux-gnueabi/, EPREFIX=/opt/gentoo. I'd |
23 |
expect EROOT to be ${EPREFIX}${ROOT}, therefore, |
24 |
/opt/gentoo/usr/armv7a-hardfloat-linux-gnueabi/. At present |
25 |
EROOT=/usr/armv7a-hardfloat-linux-gnueabi/opt/gentoo/, which is |
26 |
completely useless. |
27 |
|
28 |
Cheers, |
29 |
Benda |