I do have ldd (Cygwin) and it can show what DLLs the .exe will load.
That's determined by the PATH, and with the PATH corrected it is
choosing the right version. My understanding is that Windows does not
delay loading the DLL unless the app is linked with /DELAYLOAD, which is
not the case
Good to know. Now I don't understand why it occurs. My testing seems to
show that we don't even enter hwloc_topology_init(). If Windows lazily
loads DLLs, it could mean that libhwloc-15.dll is only loaded when the
first hwloc function is called, and that loading would fail for some
reason such as
That was it - the older DLL was in the path. Thanks for looking into it.
--Jon
On 7/22/2020 6:02 AM, Brice Goglin wrote:
Hello Jon
Sorry the delay. I finally got some time to look at this. I can only
reproduce the issue when I am compiling against hwloc 2.0.4 and using
2.2.0 at runtime
Le 01/07/2020 à 15:55, Jon Dart a écrit :
> On 6/30/2020 4:00 PM, Brice Goglin wrote:
>>
>> Hello
>>
>> We don't have many windows-specific changes in 2.1 except some late
>> MSVC-related changes added after rc1. Can you try 2.1.0rc1 instead of
>> 2.1.0? It's not visible on the download page but
On 6/30/2020 4:00 PM, Brice Goglin wrote:
Hello
We don't have many windows-specific changes in 2.1 except some late
MSVC-related changes added after rc1. Can you try 2.1.0rc1 instead of
2.1.0? It's not visible on the download page but it's actually
available, for instance at
Hello
We don't have many windows-specific changes in 2.1 except some late
MSVC-related changes added after rc1. Can you try 2.1.0rc1 instead of
2.1.0? It's not visible on the download page but it's actually
available, for instance at
