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