Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-11 Thread Brice Goglin
Hello We now have a CI slave running cygwin on Windows 10. Everything should work fine in v2.0.3. In the meantime, the only patch that you need to add on top of what you sent earlier is: https://github.com/open-mpi/hwloc/commit/3ac7bd3b3bddd763b2e58eff77a2104ea79230af (for fixing

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-02 Thread Brice Goglin
OK I pushed your #ifdef fixes and I fixed the printf warning. I opened 3 issues related to x86 cpuid and OpenProcess failing in lstopo --ps. Hopefully we'll find a way to play with cygwin here for real in the near future, and then add that config to our CI. Brice

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-02 Thread Marco Atzeri
Am 02.10.2018 um 07:47 schrieb Brice Goglin: Le 02/10/2018 à 00:28, Marco Atzeri a écrit : Am 01.10.2018 um 19:57 schrieb Brice Goglin: Le 01/10/2018 à 19:22, Marco Atzeri a écrit : Your own machine doesn't matter. None is these tests look at your CPU or topology. *All* of them on all x86

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-01 Thread Brice Goglin
Le 02/10/2018 à 00:28, Marco Atzeri a écrit : > Am 01.10.2018 um 19:57 schrieb Brice Goglin: >> Le 01/10/2018 à 19:22, Marco Atzeri a écrit : >>> >> >> Your own machine doesn't matter. None is these tests look at your CPU or >> topology. *All* of them on all x86 machines. >> CPUID are emulated by

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-01 Thread Marco Atzeri
Am 01.10.2018 um 19:57 schrieb Brice Goglin: Le 01/10/2018 à 19:22, Marco Atzeri a écrit : Your own machine doesn't matter. None is these tests look at your CPU or topology. *All* of them on all x86 machines. CPUID are emulated by reading files, nothing is read from your local machine

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-01 Thread Brice Goglin
Le 01/10/2018 à 19:22, Marco Atzeri a écrit : > >> Unfortunately that test script isn't easy to debug in the v2.x branch. >> If that OpenProcess is where things fail, I assume that the line that >> fails is "lstopo --ps". On MinGW, that code is ignored because /proc >> doesn't exist. Does /proc

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-01 Thread Brice Goglin
Le 01/10/2018 à 17:27, Marco Atzeri a écrit : > Am 30.09.2018 um 20:11 schrieb Samuel Thibault: >> Marco Atzeri, le dim. 30 sept. 2018 20:02:59 +0200, a ecrit: >>> also adding a HWLOC_DECLSPEC on the first case distances.c:347 >>> does not solve the issue as the two declaration are not the same.

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-10-01 Thread Marco Atzeri
Am 30.09.2018 um 20:11 schrieb Samuel Thibault: Marco Atzeri, le dim. 30 sept. 2018 20:02:59 +0200, a ecrit: also adding a HWLOC_DECLSPEC on the first case distances.c:347 does not solve the issue as the two declaration are not the same. Suggestion ? Perhaps use hwloc_uint64_t instead of

Re: [hwloc-devel] hwloc_distances_add conflicting declaration

2018-09-30 Thread Samuel Thibault
Marco Atzeri, le dim. 30 sept. 2018 20:02:59 +0200, a ecrit: > also adding a HWLOC_DECLSPEC on the first case distances.c:347 > does not solve the issue as the two declaration are not the same. > > Suggestion ? Perhaps use hwloc_uint64_t instead of uint64_t in hwloc/distances.c? Samuel