<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"></div><div dir="ltr"><br></div><div dir="ltr"><br>On 9 Sep 2019, at 11:21 pm, Horst Simon <<a href="mailto:horst.simon@optusnet.com.au">horst.simon@optusnet.com.au</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><meta http-equiv="Content-Type" content="text/html; charset=utf-8">Hi Chris,<div class=""><br class=""></div><div class="">Failing machine output Macbook Pro 13 inch 2010</div><div class="">machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 XSAVE</div><div class=""><b class=""><br class=""></b></div><div class="">Working machine output Macbook Pro 15 inch 2010</div><div class=""><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 SSE4.2 POPCNT AES PCID</span></div></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">I can not see any reference to AVX on either CPU.</span></div></div></blockquote><div><br></div><div>AVX was just a guess. Based in the above it could be sse 4.2 that is the issue. The machine that is failing lacks this (which actually makes that cpu pretty old I would guess)</div><br><blockquote type="cite"><div dir="ltr"><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""> I downloaded the rspamd tar ball from macports, is there documentation on how to make changes and how to disable certain feature for the build?</span></div></div></blockquote><div><br></div><div>I do not know exactly what tarball you are referring to, but thats not how its done in macports. You will need to checkout the ports tree from github, or just the portfile in question, and patch that accordingly. See</div><div><br></div><div><a href="https://guide.macports.org/chunked/development.html">https://guide.macports.org/chunked/development.html</a></div><div><br></div><div>For more details.</div><div><br></div><div>Chris</div><br><blockquote type="cite"><div dir="ltr"><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">I use the 13 inch MacBook mainly as aptest machine so it is not to important if it doesn’t work as long as I have a working one.</span></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Thanks and Regards,</span></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Horst</span></div><div style="margin: 0px; font-stretch: normal; line-height: normal;" class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><div><blockquote type="cite" class=""><div class="">On 09 Sep 2019, at 23:21, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk" class="">jonesc@hep.phy.cam.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">what does<br class=""><br class="">sysctl -a | grep machdep.cpu.features<br class=""><br class="">give on the machine with the issues ? Does it list AVX2 ?<br class=""><br class="">rspamd was recently (by Steven Smith) given a bit of an overhaul, adding a few new deps and features, see the history of recent commits at<br class=""><br class=""><a href="https://github.com/macports/macports-ports/commits/master/mail/rspamd/Portfile" class="">https://github.com/macports/macports-ports/commits/master/mail/rspamd/Portfile</a><br class=""><br class="">it could be one of these is giving the problems, not the rspamd build itself. Try seeing if build one of the various deps from source helps.<br class=""><br class="">Chris<br class=""><br class="">On 09/09/2019 2:11 pm, Horst Simon wrote:<br class=""><blockquote type="cite" class="">I tried a build from source and it showed following for AVX<br class="">-- Performing Test C_HAS_AVX_1<br class="">-- Performing Test C_HAS_AVX_1 - Failed<br class="">-- Performing Test C_HAS_AVX_2<br class="">-- Performing Test C_HAS_AVX_2 - Success<br class="">-- Performing Test C_HAS_AVX2_1<br class="">-- Performing Test C_HAS_AVX2_1 - Failed<br class="">-- Performing Test C_HAS_AVX2_2<br class="">-- Performing Test C_HAS_AVX2_2 - Success<br class="">Will download the tar file and try with AVX disabled. I tried it on my iMac 2017 macOS 10.14.6 and it works fine on this one.<br class="">Regards,<br class="">*Horst Simon*<br class=""><blockquote type="cite" class="">On 09 Sep 2019, at 21:47, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk">jonesc@hep.phy.cam.ac.uk</a> <<a href="mailto:jonesc@hep.phy.cam.ac.uk">mailto:jonesc@hep.phy.cam.ac.uk</a>>> wrote:<br class=""><br class=""><br class="">On 09/09/2019 12:35 pm, Horst Simon wrote:<br class=""><blockquote type="cite" class="">Thanks for the replies, it is a Macbook Pro 2011 i try to run it on,<br class=""></blockquote><br class="">In which case I am going to bet the issue is your machine does not support avx2, which the default build of rspamd apears to be enabling.<br class=""><br class="">One easy way to check is to force a build from source, and see what that does. The build should then detect what the build machine, your machine, supports and thus disable what is causing the problem.<br class=""><br class="">If that works, then please file a ticket at<br class=""><br class=""><a href="https://trac.macports.org/wiki/Tickets">https://trac.macports.org/wiki/Tickets</a><br class=""><br class="">asking the maintainer or spamd to address the issue, by disabling the automatic CPU capabilities detection in the default builds.<br class=""><br class="">cheers Chris<br class=""><br class=""><br class=""><blockquote type="cite" class="">will try the suggestions<br class="">Horst<br class=""><blockquote type="cite" class="">*Horst Simon*<br class="">Mobile: +61 414 303-433 <<a href="tel:+61%20414%20303-433">tel:+61%20414%20303-433</a>><br class="">Phone: +61 3 8555-2322 <<a href="tel:+61%203%208555-2322">tel:+61%203%208555-2322</a>><br class="">Email: <a href="mailto:horst.simon@optusnet.com.au">horst.simon@optusnet.com.au</a> <<a href="mailto:horst.simopn@optusnet.com.au">mailto:horst.simopn@optusnet.com.au</a>><br class="">______________________________________________________________________<br class="">Please consider your environmental<br class="">responsibility before printing this email.<br class=""><br class="">This message (including any attachments) is intended only for the use of the individual or entity<br class="">to which it is addressed and may contain information that is non-public, proprietary, privileged,<br class="">confidential, and exempt from disclosure under applicable law or may constitute as attorney work<br class="">product. If you are not the intended recipient, you are hereby notified that any use, dissemination,<br class="">distribution, or copying of this communication is strictly prohibited. If you have received this<br class="">communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile<br class="">or (ii) delete this message immediately if this is an electronic communication.<br class=""></blockquote>On 9 Sep 2019, at 20:57, Chris Jones <<a href="mailto:jonesc@hep.phy.cam.ac.uk">jonesc@hep.phy.cam.ac.uk</a> <<a href="mailto:jonesc@hep.phy.cam.ac.uk">mailto:jonesc@hep.phy.cam.ac.uk</a>>> wrote:<br class=""><blockquote type="cite" class=""><br class=""><blockquote type="cite" class="">The first thing to do is check the buildbot logs, to see if you can work out what CPU feature the builds are enabling, and then proceed from there.<br class=""><a href="https://ports.macports.org/port/rspamd/builds">https://ports.macports.org/port/rspamd/builds</a><br class=""></blockquote><br class="">from the 10.13 configure step<br class=""><br class="">-- Performing Test HAVE_AVX2_C_COMPILER<br class="">-- Performing Test HAVE_AVX2_C_COMPILER - Success<br class="">-- Compilation of avx asm set is supported<br class="">-- Compilation of sse2 asm set is supported<br class="">-- Compilation of sse3 asm set is supported<br class="">-- Compilation of ssse3 asm set is supported<br class="">-- Compilation of sse41 asm set is supported<br class="">-- Compilation of sse42 asm set is supported<br class="">-- AVX2 support is added<br class="">-- AVX support is added<br class="">-- SSE2 support is added<br class="">-- SSE41 support is added<br class="">-- SSE42 support is added<br class=""><br class="">enabling AVX(2) is likely the issue here, as this is not guaranteed to be available. My 2011 mac mini running 10.13 does not have AVX2, for instance.<br class=""><br class="">So the (default) build needs to be configured to not enable AVX, even if the host CPU (buildbot) supports it.<br class=""><br class="">Chris<br class=""><br class=""><blockquote type="cite" class="">Chris<br class=""></blockquote></blockquote></blockquote></blockquote></blockquote></div></div></blockquote></div><br class=""></div></div></blockquote></body></html>