| 1 |
On Sat, 2 Jan 2016 13:27:52 -0500 waltdnes@××××××××.org wrote: |
| 2 |
> On Sat, Jan 02, 2016 at 02:56:58PM +0300, Andrew Savchenko wrote |
| 3 |
> |
| 4 |
> > For 32-bit distcc on 64-bit host there is no need to chroot or |
| 5 |
> > create VM (hey, they're hellishly slow!). Just add -m32 to your |
| 6 |
> > *FLAGS to force 32-bit arch. (In some rare cases ebuild ignores |
| 7 |
> > {C,CXX,F,FC}FLAGS, while this is a bug and should be fixed, this |
| 8 |
> > can be worked around on distcc server by forcing -m32 for each |
| 9 |
> > gcc call. |
| 10 |
> |
| 11 |
> -m32 in a 64-environment works for "Hello World". More complex code |
| 12 |
> that requires arch-specific headers and libs will have problems. It |
| 13 |
> "works" with Gentoo distcc. |
| 14 |
|
| 15 |
No, it works for the entire system and for 8 years here, just don't |
| 16 |
use pump mode. I don't use it because my 32-bit and 64-bit hosts |
| 17 |
have quite a different software installed. Are you are sure |
| 18 |
packages on both your host are identical in their list and |
| 19 |
versions? Pump mode just have too many limitations to be used |
| 20 |
outside of a cluster of (almost) identical hosts. |
| 21 |
|
| 22 |
Best regards, |
| 23 |
Andrew Savchenko |
Archives