1 |
Alternatively, what I've done in the past, was actually natively compile |
2 |
badly behaved packages using Qemu/ARM. |
3 |
|
4 |
This is naturally slightly slower. |
5 |
|
6 |
Chris |
7 |
|
8 |
Karl Hiramoto wrote: |
9 |
> Petric Frank wrote: |
10 |
>> Hello, |
11 |
>> |
12 |
>> i've read the mail from Corey <corey@...> (dd. 2006-11-20 03:13:19 GMT). |
13 |
>> |
14 |
>> The problem is that the build process compiles a test program for the |
15 |
>> destination platform and afterwards it tries to execute it. |
16 |
>> This will never work when cross compiling. |
17 |
>> |
18 |
>> Are there any workarounds available (patches for the ebuild, etc.) ? |
19 |
>> |
20 |
>> regards |
21 |
>> Petric |
22 |
>> |
23 |
> |
24 |
> There are a lot of packages like this that come this way from upstream |
25 |
> |
26 |
> Options that have worked for me |
27 |
> 1. modify the configure script and/or makefiles to not run the test program |
28 |
> |
29 |
> 2. In a few cases i complied gcc for my ARM platform, then compiled |
30 |
> natively.. I think perl was one of these.. It took hours to compile.. |
31 |
> |
32 |
> -- |
33 |
> Karl. |
34 |
-- |
35 |
gentoo-embedded@g.o mailing list |