On Monday, June 27 2016, Aaron M. Ucko wrote: > Builds of newlisp for many Linux architectures failed due to its > explicit use of -m32 or -m64. Although these flags can be redundant > on several architectures, they're never necessary for fully native > compilation, and can cause problems on some architectures, most often > because the compiler doesn't support them there. The x32 failure also > stems from this problem: > > gcc -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -m32 -Wall > -Wno-strict-aliasing -Wno-long-long -c -O2 -g -DREADLINE > -DSUPPORT_UTF8 -DLINUX -DFFI -I/usr/local/lib/libffi-3.0.13/include -g > -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security > newlisp.c > In file included from newlisp.c:20:0: > newlisp.h:118:17: fatal error: ffi.h: No such file or directory > > The use of here makes the compiler look for i386 versions of > architecture-dependent headers like ffi.h, which aren't normally > present there. > > Please do not use these flags on any Debian architecture.
I almost removed the flags before uploading the package, but decided to let them there. Anyway, thanks for the report, I'll take a look at it later today. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
signature.asc
Description: PGP signature
