[arch-multilib] Bug with lib32-zlib PKGBUILD
remyoudompheng at gmail.com
Sat Aug 28 12:38:45 EDT 2010
Ng Oon-Ee <ngoonee at gmail.com> wrote:
> On Sat, 2010-08-28 at 18:09 +0200, Rémy Oudompheng wrote:
>> 32-bit gcc uses -march=x86_64 instead of -march=i686.
> Ah. That's true. Just tried it, compiling with -march=i686 and -O3
> So here's the combinations that work for me:-
> a) -march=x86_64 and no optimization
> b) -march=i686 and -O3
> If both of these can be attributed to the oddities of the OpenSong
> compiled binary then I'll just leave it at that. Will just have to
> remember to manually patch lib32=zlib when/if it updates (don't think
> that's very often honestly).
> I wonder about the validity of compiling lib32 packages with
> -march=i686, should it be done that way? Is it, in other distros?
I would say using -march=(some real 32-bit architecture) for the multilib
repo would be better for compatibility with binary packages. Having
CFLAGS="-march=x86_64 -m32" doesn't look OK.
More information about the arch-multilib