| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 01/02/2016 01:27 PM, waltdnes@××××××××.org wrote: |
| 5 |
> On Sat, Jan 02, 2016 at 02:56:58PM +0300, Andrew Savchenko wrote |
| 6 |
> |
| 7 |
>> For 32-bit distcc on 64-bit host there is no need to chroot or |
| 8 |
>> create VM (hey, they're hellishly slow!). Just add -m32 to your |
| 9 |
>> *FLAGS to force 32-bit arch. (In some rare cases ebuild ignores |
| 10 |
>> {C,CXX,F,FC}FLAGS, while this is a bug and should be fixed, this |
| 11 |
>> can be worked around on distcc server by forcing -m32 for each |
| 12 |
>> gcc call. |
| 13 |
> |
| 14 |
> -m32 in a 64-environment works for "Hello World". More complex |
| 15 |
> code that requires arch-specific headers and libs will have |
| 16 |
> problems. It "works" with Gentoo distcc. Rather than erroring |
| 17 |
> out, it sends the work back to my Atom netbook, and says "Sorry, |
| 18 |
> you have to do this yourself". This defeats the point of distcc. |
| 19 |
> Outside of Gentoo distcc, the errors stop the build. So yes, I do |
| 20 |
> need a 32-bit environment. |
| 21 |
> |
| 22 |
> I ran into this, trying to manually build Pale Moon (a Firefox |
| 23 |
> fork) for my Atom netbook from a 64-bit environment. It doesn't |
| 24 |
> work. Mozilla and its derivatives all use the same weird build |
| 25 |
> scripts. See... |
| 26 |
> https://forum.palemoon.org/viewtopic.php?f=37&t=10002 |
| 27 |
> |
| 28 |
> I eventually re-installed 32-bit Gentoo on my ancient Core2 |
| 29 |
> machine. Since it only has 3 gigs of RAM, it's not losing anything. |
| 30 |
> It successfully built the Atom-specific branch (a bunch of |
| 31 |
> "web-developer" stuff removed) for my netbook. My netbook is |
| 32 |
> actually "-march=bonnell" |
| 33 |
> https://en.wikipedia.org/wiki/Bonnell_%28microarchitecture%29 I |
| 34 |
> selected that instead of the generic "-march=atom". |
| 35 |
> |
| 36 |
> By the way, Atom-specific-source Pale Moon builds are really snappy |
| 37 |
> on a newer machine when built with "-march=native". On the other |
| 38 |
> hand, the Firefox developers have utterly gone off the deep end. |
| 39 |
> The Atrocious^H^H^H^H^H^H^H^H^H Australis GUI was the final straw |
| 40 |
> that drove me away. |
| 41 |
> |
| 42 |
|
| 43 |
|
| 44 |
I think that you misunderstand how distcc works. The distcc process |
| 45 |
*only* sends preprocessed data to the remote machine, and *only* gets |
| 46 |
back object code. All preprocessing (headers) and linking (libraries, |
| 47 |
combining *.o files) is *always* done on the host that the packages |
| 48 |
will be used on, because slightly different versions would otherwise |
| 49 |
cause problems. So your problem with "arch-specific headers and |
| 50 |
libraries" *always* causes that part to run on the netbook, even if |
| 51 |
the remote distcc server is exactly the same arch, etc. |
| 52 |
|
| 53 |
- -- |
| 54 |
Jonathan Callen |
| 55 |
-----BEGIN PGP SIGNATURE----- |
| 56 |
Version: GnuPG v2 |
| 57 |
|
| 58 |
iQIcBAEBCgAGBQJWiFzXAAoJEEIQbvYRB3mgwZIP/1bb2cJ5d5DselrzYQd48wXJ |
| 59 |
LnftAoBgUtYjc866EYPMYJchW+xQtrSJzuHEPuWDjiwIbgRA7zQzHCYRwJWNXrry |
| 60 |
iZPVKaxnTumU/ttUZHZHiBtga5HULwAPkSwCBPrFpFYXuvghNuGIG4Kdz+8a18Ef |
| 61 |
hFIbY/qRIXJgNq8bIekoOY7ED1/27mPcNW1BReJoCOo+oTPp6QqbE/nZ+rDtQPBi |
| 62 |
Gx8jtJptaHtQ7kCN4ddDfgYQry0/yU5QaScLwzExDXAIAw3I14ecMMu8AtSpacPx |
| 63 |
UZ5HOb/iuV4tUcB5yEhbasFAgs7i36Cr0WtcbFZ4XaUA6m92ldwiQrAMMRMT3Vxm |
| 64 |
X5Hemtckw9feFxvJw5SEupLbWTG13LZ/pZK03o8DgJIVaEkZcis6RhBZZCwZzuDq |
| 65 |
erX3xcsS+vHRrIrZKIbA7Fwc3ronbToH45EcXfdobMLlUp5wx1W2lB1WcS/a8WtJ |
| 66 |
L5+c3GmKbjg6HAarZ3kWTHhr0X20J8SLkx2pwUYn7kX6bZEgHpIsyb6I+2ZHkfq4 |
| 67 |
K1Jc96WVfFwQSu77TPhURUcFMPXlv1zjKnTtwesgLvSVxKSq5wZu/295dkmqeuyg |
| 68 |
of2w5wrWaq7DZCPkNVemtknVXeFgAUglkpr9M4DWG8DN4vTlN5naG8D3XPxprT3B |
| 69 |
KJCTrSGYoRe/V6Fk/pJ/ |
| 70 |
=mMUw |
| 71 |
-----END PGP SIGNATURE----- |
Archives