Thanks for the replies, it is a Macbook Pro 2011 i try to run it on, will try the suggestions Horst
> Horst Simon > Mobile: +61 414 303-433 > Phone: +61 3 8555-2322 > Email: horst.si...@optusnet.com.au > ______________________________________________________________________ > Please consider your environmental > responsibility before printing this email. > > This message (including any attachments) is intended only for the use of the > individual or entity > to which it is addressed and may contain information that is non-public, > proprietary, privileged, > confidential, and exempt from disclosure under applicable law or may > constitute as attorney work > product. If you are not the intended recipient, you are hereby notified that > any use, dissemination, > distribution, or copying of this communication is strictly prohibited. If you > have received this > communication in error, notify us immediately by telephone and (i) destroy > this message if a facsimile > or (ii) delete this message immediately if this is an electronic > communication. > On 9 Sep 2019, at 20:57, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > >> 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. >> https://ports.macports.org/port/rspamd/builds > > from the 10.13 configure step > > -- Performing Test HAVE_AVX2_C_COMPILER > -- Performing Test HAVE_AVX2_C_COMPILER - Success > -- Compilation of avx asm set is supported > -- Compilation of sse2 asm set is supported > -- Compilation of sse3 asm set is supported > -- Compilation of ssse3 asm set is supported > -- Compilation of sse41 asm set is supported > -- Compilation of sse42 asm set is supported > -- AVX2 support is added > -- AVX support is added > -- SSE2 support is added > -- SSE41 support is added > -- SSE42 support is added > > 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. > > So the (default) build needs to be configured to not enable AVX, even if the > host CPU (buildbot) supports it. > > Chris > >> Chris
