| 1 |
Michael Weyershäuser wrote: |
| 2 |
> Daniel Iliev wrote: |
| 3 |
> |
| 4 |
>> I tried to use a x86 pc to aid the compiling of packages for amd64 via |
| 5 |
>> distcc. I followed the official "DistCC Cross-compiling Guide" [1] but I |
| 6 |
>> had no luck. Is it possible at all, am I doing something wrong or there |
| 7 |
>> is a bug? |
| 8 |
>> |
| 9 |
>> [1] http://www.gentoo.org/doc/en/cross-compiling-distcc.xml |
| 10 |
>> |
| 11 |
>> |
| 12 |
> I'm running such a setup for about 6 months now and I have never run |
| 13 |
> into any package not compiling due to the crossdev environment (and I |
| 14 |
> compile quite a lot of packages as an amd64 AT). So this should in |
| 15 |
> general work without any trouble or patches. |
| 16 |
> |
| 17 |
>> The i686 pc gives: |
| 18 |
>> |
| 19 |
>> localhost ~ # crossdev -t x86_64-pc-linux-gnu |
| 20 |
>> * You need to set PORTDIR_OVERLAY in your make.conf. |
| 21 |
>> * A standard setting is /usr/local/portage |
| 22 |
>> localhost ~ # echo PORTDIR_OVERLAY=/usr/local/portage >> /etc/make.conf |
| 23 |
>> localhost ~ # crossdev -t x86_64-pc-linux-gnu |
| 24 |
>> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage' |
| 25 |
>> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage' |
| 26 |
>> |
| 27 |
>> localhost ~ # mkdir /usr/local/portage |
| 28 |
>> localhost ~ # crossdev -t x86_64-pc-linux-gnu |
| 29 |
>> -------------------------------------------------------------------------------- |
| 30 |
>> * Host Portage ARCH: x86 |
| 31 |
>> * Target Portage ARCH: amd64 |
| 32 |
>> * Target System: x86_64-pc-linux-gnu |
| 33 |
>> * Stage: 4 (C/C++ compiler) |
| 34 |
>> |
| 35 |
>> * binutils: binutils-[latest] |
| 36 |
>> * gcc: gcc-[latest] |
| 37 |
>> * headers: linux-headers-[latest] |
| 38 |
>> * libc: glibc-[latest] |
| 39 |
>> |
| 40 |
>> * PORTDIR_OVERLAY: /usr/local/portage |
| 41 |
>> * PORT_LOGDIR: /var/log/portage |
| 42 |
>> * PKGDIR: /usr/portage/packages/cross/x86_64-pc-linux-gnu |
| 43 |
>> * PORTAGE_TMPDIR: /tmp/cross/x86_64-pc-linux-gnu |
| 44 |
>> _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ |
| 45 |
>> - _ - |
| 46 |
>> * Forcing the latest versions of binutils-config/gcc-config |
| 47 |
>> ... [ ok ] |
| 48 |
>> * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log |
| 49 |
>> * Emerging cross-binutils ... |
| 50 |
>> |
| 51 |
>> * binutils failed :( |
| 52 |
>> * If you file a bug, please attach the following logfiles: |
| 53 |
>> * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log |
| 54 |
>> * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log |
| 55 |
>> |
| 56 |
> |
| 57 |
> If this was a bug I would close it as RESOLVED NEEDINFO right now. |
| 58 |
> Please attach these two log files if you want anybody to be able to help |
| 59 |
> you ;) |
| 60 |
> |
| 61 |
> |
| 62 |
> |
| 63 |
|
| 64 |
|
| 65 |
I saw an update for gcc and after emerging it I decided to try again. |
| 66 |
Four steps forward but the final goal is not achieved yet. |
| 67 |
|
| 68 |
|
| 69 |
crossdev -t x86_64-pc-linux-gnu |
| 70 |
-------------------------------------------------------------------------------- |
| 71 |
* Host Portage ARCH: x86 |
| 72 |
* Target Portage ARCH: amd64 |
| 73 |
* Target System: x86_64-pc-linux-gnu |
| 74 |
* Stage: 4 (C/C++ compiler) |
| 75 |
|
| 76 |
* binutils: binutils-[latest] |
| 77 |
* gcc: gcc-[latest] |
| 78 |
* headers: linux-headers-[latest] |
| 79 |
* libc: glibc-[latest] |
| 80 |
|
| 81 |
* PORTDIR_OVERLAY: /usr/local/portage |
| 82 |
* PORT_LOGDIR: /var/log/portage |
| 83 |
* PKGDIR: /usr/portage/packages/cross/x86_64-pc-linux-gnu |
| 84 |
* PORTAGE_TMPDIR: /tmp/cross/x86_64-pc-linux-gnu |
| 85 |
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ |
| 86 |
- _ - |
| 87 |
* Forcing the latest versions of binutils-config/gcc-config |
| 88 |
... [ ok ] |
| 89 |
* Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log |
| 90 |
* Emerging cross-binutils |
| 91 |
... [ ok ] |
| 92 |
* Log: /var/log/portage/cross-x86_64-pc-linux-gnu-gcc-stage1.log |
| 93 |
* Emerging cross-gcc-stage1 |
| 94 |
... [ ok ] |
| 95 |
* Log: /var/log/portage/cross-x86_64-pc-linux-gnu-linux-headers.log |
| 96 |
* Emerging cross-linux-headers |
| 97 |
... [ ok ] |
| 98 |
* Log: /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log |
| 99 |
* Emerging cross-glibc ... |
| 100 |
|
| 101 |
* glibc failed :( |
| 102 |
* If you file a bug, please attach the following logfiles: |
| 103 |
* /var/log/portage/cross-x86_64-pc-linux-gnu-info.log |
| 104 |
* /var/log/portage/cross-x86_64-pc-linux-gnu-glibc.log |
| 105 |
|
| 106 |
|
| 107 |
The last file is attached in this email message as a bzip2 archive. At |
| 108 |
its end this log file reads: |
| 109 |
|
| 110 |
>checking for forced unwind support... no |
| 111 |
>configure: error: forced unwind support is required |
| 112 |
|
| 113 |
|
| 114 |
Unfortunately I have no idea what this means. Any suggestions, please? |
| 115 |
|
| 116 |
-- |
| 117 |
Best regards, |
| 118 |
Daniel |
| 119 |
|
| 120 |
|
| 121 |
-- |
| 122 |
gentoo-amd64@g.o mailing list |
Archives