Bug#814138: wimlib: FTBFS on x32: operand type mismatch for `add'

[John Paul Adrian Glaubitz]

Hi Aaron!

> Hrm, yeah, I don't see an x32 porterbox.

It's trivial to setup your own x32 chroot, see:

> https://wiki.debian.org/X32Port

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#814138: wimlib: FTBFS on x32: operand type mismatch for `add'

[Aaron M. Ucko]

Hilko Bengen  writes:

> However, I can't test this.

Hrm, yeah, I don't see an x32 porterbox.  That change sounds correct,
though.  Thanks for the quick response!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#814138: wimlib: FTBFS on x32: operand type mismatch for `add'

[Hilko Bengen]

* Aaron M. Ucko:

> Source: wimlib
> Version: 1.8.3-1
> Severity: important
> Justification: fails to build from source
>
> The x32 build of wimlib failed:
>
>   src/lzms_common.c: Assembler messages:
>   src/lzms_common.c:393: Error: operand type mismatch for `add'
>   make[3]: *** [src/libwim_la-lzms_common.lo] Error 1

This is part of a block which is guarded with
"#ifdef __x86_64__ … #endif".

I suppose one could extend that #ifdef to exclude x32; according to
, the __ILP32__ seems to be the correct
define.

However, I can't test this.

Cheers,
-Hilko

Bug#814138: wimlib: FTBFS on x32: operand type mismatch for `add'

[Aaron M. Ucko]

Source: wimlib
Version: 1.8.3-1
Severity: important
Justification: fails to build from source

The x32 build of wimlib failed:

  src/lzms_common.c: Assembler messages:
  src/lzms_common.c:393: Error: operand type mismatch for `add'
  make[3]: *** [src/libwim_la-lzms_common.lo] Error 1

Could you please take a look?

Thanks!