Bug#828806: newlisp: FTBFS: explicit -m32/-m64 problematic

2016-06-28 Thread Sergio Durigan Junior
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

Bug#828806: newlisp: FTBFS: explicit -m32/-m64 problematic

2016-06-27 Thread Aaron M. Ucko
Source: newlisp Version: 10.7.0-1 Severity: important Justification: fails to build from source 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 c