| 1 |
On 2017-07-20 05:59, R0b0t1 <r030t1@×××××.com> wrote: |
| 2 |
> On Thu, Jul 20, 2017 at 12:42 AM, Danny YUE <sheepduke@×××××.com> wrote: |
| 3 |
>> Hi guys, |
| 4 |
>> |
| 5 |
>> I am setting up cross compiling environment for my newly bought |
| 6 |
>> Raspberry Pi 3, under the guide of: |
| 7 |
>> https://wiki.gentoo.org/wiki/Raspberry_Pi |
| 8 |
>> https://wiki.gentoo.org/wiki/Raspberry_Pi/Quick_Install_Guide |
| 9 |
>> |
| 10 |
>> My original idea was to use crossdev to cross compile packages on my PC |
| 11 |
>> and install binaries on RPI. |
| 12 |
>> However I found it really nasty because it kept giving me the error |
| 13 |
>> message about "libintl: no such file or directory" during compilation of |
| 14 |
>> packages such as attr, python etc. |
| 15 |
>> |
| 16 |
>> And if some (even very few) packages fail to build on the PC, it is |
| 17 |
>> hardly possible to keep PC and RPI 'consistent'. |
| 18 |
>> (Yes, I did setup the 'make.profile' symlink to the right place.) |
| 19 |
>> |
| 20 |
>> So my question is: |
| 21 |
>> 1) If some packages are *doomed* to fail, how do you keep the |
| 22 |
>> emerge world environment consistency between PC and RPI? |
| 23 |
>> Or is my understanding of this method incorrect? |
| 24 |
>> |
| 25 |
> |
| 26 |
> Match compilation and USE flags. |
| 27 |
> |
| 28 |
>> 2) If it is not really a good idea to use crossdev, which one do you |
| 29 |
>> recommend between distcc and chroot method? |
| 30 |
>> (I googled but did not really get one answer about compilation speed.) |
| 31 |
>> |
| 32 |
> |
| 33 |
> You should be able to mix crossdev compiled packages freely with |
| 34 |
> device compiled ones. Incompatible packages will be ignored and it |
| 35 |
> will try to recompile a package with matching flags, so pay attention. |
| 36 |
> If you need to compile something on device then I suspect you want to |
| 37 |
> use distcc if at all possible. |
| 38 |
> |
| 39 |
Thanks for your reply. :-) |
| 40 |
|
| 41 |
Well, yes. But do you know how is distcc compared with chroot referring |
| 42 |
to compilation speed? |
| 43 |
|
| 44 |
> Please submit a bug report for packages that don't compile. You |
| 45 |
> probably want to do it on the Gentoo tracker. These tend to be |
| 46 |
> problems with autoconf, but developers seem to be reluctant to |
| 47 |
> learning about the autoconf tests they make use of or providing fixes |
| 48 |
> for them even though they're likely the people most capable creating |
| 49 |
> fixes. The autoconf developers do not seem to have any idea about how |
| 50 |
> to deal with cross compilation failures in a centralized way. |
| 51 |
> |
| 52 |
>> Thanks in advance for any potential help. ;-) |
| 53 |
>> |
| 54 |
>> P.S. Does anyone have any idea about the 'libintl' error? I googled a |
| 55 |
>> lot but it seems that it should be part of glibc... |
| 56 |
> |
| 57 |
> Can you post the full output of the error you're receiving? |
| 58 |
|
| 59 |
Sorry, I am not using my PC currently. |
| 60 |
|
| 61 |
I will re-install cross toolchain later on today and post the result |
| 62 |
here. |
| 63 |
|
| 64 |
Thanks again. |
| 65 |
|
| 66 |
Danny |
Archives