Re: gcc possibly generating invalid assembler

2017-04-19 Thread Wouter Verhelst
On Wed, Apr 19, 2017 at 09:39:38AM +0200, Wouter Verhelst wrote: > due to lack of pthread support, or the optimization level. Feels like > someone failed to read the automake documentation properly (CFLAGS is > supposed to remain unset; and indeed checking out configure.ac reveals > some CFLAGS mun

Re: gcc possibly generating invalid assembler

2017-04-19 Thread Wouter Verhelst
On Wed, Apr 19, 2017 at 09:39:38AM +0200, Wouter Verhelst wrote: > Anyway, that means the most likely cause is the optimizer. side note: there actually is some inline assembly, but it looks like that's coming from places like /usr/m68k-linux-gnu/include/byteswap.h etc, so not the cause of this pro

Re: gcc possibly generating invalid assembler

2017-04-19 Thread John Paul Adrian Glaubitz
On 04/19/2017 09:39 AM, Wouter Verhelst wrote: > Good point, but nope, even with 'CFLAGS+=-save-temps' it succeeds. For me, building the package succeeds with the following added to debian/rules: ifeq ($(DEB_HOST_ARCH_CPU), m68k) export DEB_CFLAGS_MAINT_APPEND += -O0 endif > Next attempt

Re: gcc possibly generating invalid assembler

2017-04-19 Thread Wouter Verhelst
On Tue, Apr 18, 2017 at 08:42:32PM +0200, John Paul Adrian Glaubitz wrote: > On 04/14/2017 09:36 AM, Wouter Verhelst wrote: > > Then I ran 'make CFLAGS=-save-temps' to see whether it perhaps did add > > some inline assembly somewhere but you missed the #include and this time > > it... worked? > >