I forgot to mention: if the output of ./config.guess begins with x86_64 or core2 and yet you have a recent machine, this is a misconfiguration of MPIR.
In such cases, could you please send me the output of cat /proc/cpuinfo from your machine, or otherwise tell me what the precise CPU model is for your machine, e.g. AMD Opteron R5875. Bill. On 12 June 2015 at 17:07, Bill Hart <goodwillh...@googlemail.com> wrote: > Hi all, > > I've completed all the *nix testing I can, but need help on other OS's and > arches. > > So far I have: > > Ubuntu: > ====== > k102 > penryn > bulldozer > > Gentoo: > ======= > nehalem > itanium2 > sandybridge > > Cygwin/Mingw/Msys (32/64 bit): > ================================ > haswell > > That's all the machines I currently have access to. > > If anyone has access to any of the following, test reports would be > welcome: > > Architectures: > ============== > piledriver, sparc64, ppc64, arm, arm64, mips64, netburst, atom, westmere, > k10, core2 > > OS's: > ===== > freebsd, openbsd, solaris, archlinux, mint, centos, fedora, debian, > opensuse > > Here is the set of commands to test mpir: > > wget http://mpir.org/mpir-2.7.0-alpha13.tar.bz2 > tar -xvf mpir-2.7.0-alpha13.tar.bz2 > cd mpir-2.7.0 > ./configure --enable-cxx > make -j > make -j check > > We don't require tuning values, as we already did that earlier in the > release. We are only testing at this stage. > > Bill. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
