On 5/1/20 2:19 AM, Andrea Corallo wrote: > Ashish SHUKLA writes: > > >> Hi Andrea, >> >> Sorry for the delay. >> >> Tried 02e3ffad6d9f with again with following CFLAGS, assuming by speed 0 >> you meant, -O0: >> >> -O0 -g -march=haswell -fstack-protector-strong -isystem >> /usr/local/include -fno-strict-aliasing -fstack-protector-strong >> -isystem /usr/local/include > > Hi Ashish, > > Thanks, sorry I wasn't clear. You can control the speed parameter of > the native compiler during the initial build for instance as follow: > > make BYTE_COMPILE_EXTRA_FLAGS='--eval "(setq comp-speed 0)"' -j2 > > If you could try this is an interesting test. I suspect this could be > the same bug is seen on MacOS where is observed to be working only at > speed 0. After making that change, I'm able to install it fine. -- Ashish SHUKLA