[hwloc-users] Building hwloc on Cray with /opt/cray/craype/2.5.4/bin/cc

2017-01-05 Thread Xavier LACOSTE
Hello, I'm trying to build hwloc on a cray machine with cray compiler :/opt/cray/craype/2.5.4/bin/cc I get the following error : $> CC=cc ./configure --prefix=$PWD-cc-install $> make Making all in src make[1]: Entering directory `/home/j0306818/xavier/hwloc-1.11.5/src' CC bitmap.lo

Re: [hwloc-users] Building hwloc on Cray with /opt/cray/craype/2.5.4/bin/cc

2017-01-05 Thread Xavier LACOSTE
Yes, indeed, __GNUC__ is 4 and __GNUC_MINOR__ 8 -Message d'origine- De : Samuel Thibault [mailto:samuel.thiba...@inria.fr] Envoyé : jeudi 5 janvier 2017 14:35 À : Hardware locality user list Cc : Brice Goglin Objet : Re: [hwloc-users] Building hwloc on Cray with

Re: [hwloc-users] Building hwloc on Cray with /opt/cray/craype/2.5.4/bin/cc

2017-01-05 Thread Brice Goglin
Does this even build with the cray compiler? int main(int argc, char *argv[]) { return __builtin_ffsl((unsigned long) argc); } Le 05/01/2017 14:56, Xavier LACOSTE a écrit : > > Indeed, > > > > If I had a #undef __GNUC__ in misc.h the compilation finished (I still > have the link

Re: [hwloc-users] Building hwloc on Cray with /opt/cray/craype/2.5.4/bin/cc

2017-01-05 Thread Xavier LACOSTE
Yes, with no warning, and I can also execute my a.out. $> cc toto.c $> ./a.out $> cat toto.c int main(int argc, char *argv[]) { return __builtin_ffsl((unsigned long) argc); } De : Brice Goglin [mailto:brice.gog...@inria.fr] Envoyé : jeudi 5 janvier 2017 15:03 À : Xavier LACOSTE Cc : Hardware

Re: [hwloc-users] Building hwloc on Cray with /opt/cray/craype/2.5.4/bin/cc

2017-01-05 Thread Brice Goglin
I think you are mixing hwloc libraries here. CPUType was removed a while ago (except on Solaris). And CPUVendor was widely added later. My feeling is that your lstopo uses a recent libhwloc while your test program uses an old one. Brice Le 05/01/2017 15:16, Xavier LACOSTE a écrit : > Hello

Re: [hwloc-users] Building hwloc on Cray with /opt/cray/craype/2.5.4/bin/cc

2017-01-05 Thread Xavier LACOSTE
Hello Samuel, With my test I get : CPU_Vendor : (null) Socket : CPUModel="Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz" | CPUType=x86_64 Meanwhile, the CPUVendor Field is in the generated xml. XL. -Message d'origine- De : Samuel Thibault [mailto:samuel.thiba...@inria.fr] Envoyé : jeudi