| 1 |
That is really odd ... did you use crossdev-wrapper (e.g. |
| 2 |
arm-softfloat-linux-gnueabi-emerge) ? |
| 3 |
|
| 4 |
I think I've experienced something like that before, and it was the |
| 5 |
result of an environment variable incorrectly set. |
| 6 |
|
| 7 |
You should run 'arm-softfloat-linux-gnueabi-emerge --info' and check |
| 8 |
for any oddities in the portage environment variables. Most of the |
| 9 |
important ones should start with /usr/arm-softfloat-linux-gnueabi . |
| 10 |
|
| 11 |
C |
| 12 |
|
| 13 |
On Mon, Mar 9, 2009 at 5:14 AM, Sven Rebhan <odinshorse@××××××××××.com> wrote: |
| 14 |
> 2009/3/9 Tim Erwin <taerwin@×××××.com>: |
| 15 |
>> I have set up a cross compiler but if I use ~arm in the ACCEPT_KEYWORDS in |
| 16 |
>> /usr/armv4tl-softfloat-linux-gnueabi/etc/make.conf, it wants to pull in |
| 17 |
>> packages for the host system (baselayout, openrc and e2fsprogs-lib) which |
| 18 |
>> are masked by ~amd64. Is there any reason for this? |
| 19 |
> |
| 20 |
> If you use the openmoko-overlay it shouldn't. The reason why this |
| 21 |
> happens is the gentoo dependency oddness. Namely the line |
| 22 |
> DEPEND="${RDEPEND}", as this tries to emerge everything you want on |
| 23 |
> the target also to host. However, removing this line is basically not |
| 24 |
> suggested. We need to add cross-compile dependencies to portage, but |
| 25 |
> until this happens you can test with removing ${RDEPEND} from the |
| 26 |
> DEPEND line. |
| 27 |
> |
| 28 |
> Furthermore, I would suggest to use a chroot to cross-compile your stuff! |
| 29 |
> |
| 30 |
> Best regards, |
| 31 |
> |
| 32 |
> Sven |
| 33 |
> |
| 34 |
> |
Archives