2016-01-02 12:27 GMT-06:00 <waltd...@waltdnes.org>:
> On Sat, Jan 02, 2016 at 02:56:58PM +0300, Andrew Savchenko wrote
>
>> For 32-bit distcc on 64-bit host there is no need to chroot or
>> create VM (hey, they're hellishly slow!). Just add -m32 to your
>> *FLAGS to force 32-bit arch. (In some rare cases ebuild ignores
>> {C,CXX,F,FC}FLAGS, while this is a bug and should be fixed, this
>> can be worked around on distcc server by forcing -m32 for each
>> gcc call.
>
> -m32 in a 64-environment works for "Hello World". More complex code
> that requires arch-specific headers and libs will have problems.
Then why the recently introuced multilib method of bulding 32bit
libraries for packages that need it on 64 bit works? I don't think the
devs would have bothered to introudce the variable ABI_X86 and a
mulitib eclass just to compile a 32bit Hello World.
I'm not trying to make a flame here, but don't blame the compiler,
when in this case is more likely you the user are doing something
wrong.
My guess is you are blaming the effects of CPU_FLAGS_X86 on CFLAGS.
