Could not open library 'libvips-42.dll': Failed with error 127: Procedure not found #379
Comments
|
Hi @HuBandiT, I'm not so good on Windows either. I did get ruby-vips working on win10 last year sometime when I needed it for a small project and I think it was straightforward, but of course something may have happened since then. I'll try again and see what happens. |
|
I tried reinstalling ruby on win10 and it failed :( I'm pretty sure this was working last year, so I guess there's been a regression. It's failing on the libvips DLL load which means it's managed to load libglib and libgobject successfully. I don't think there's a path issue, it must be some symbol in libvips which is not being resolved correctly. I wish it told us the name of the missing symbol. Perhaps it's libintl again? I'm out of time today, I'll look again tomorrow. |
|
(@kleisauke please don't spend any time investigating, but I don't suppose you have any immediate ideas what it might be?) |
|
Perhaps this is the same issue as the one mentioned in #364 (comment)? I'm not sure if that was ever fixed by MSYS2, I'll have a look. |
|
I tried quickly and neither of those workarounds (adding the extra pacman packages or removing the modules dir) did the trick :( |
|
Enabling the "Show loader snaps" flag on the Ruby interpreter with: "C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\gflags.exe" -i C:\Ruby32-x64\bin\ruby.exe +slsAnd when opening So, it looks like a clash between OpenSSL 3.1.0 (provided by @larskanis Can I ping you for this? Would upgrading OpenSSL to 3.2.0 in RubyInstaller fix this? Another option would be to disable Matlab support in the MSYS2 package of libvips, since libcurl is required by libhdf5, on which libmatio depends. |
|
Thanks for doing the debugging! Answering from memory, this looks like a kind of oneclick/rubyinstaller2#60 . I'll check if I can make a new release of RubyInstaller-3.2 updating to OpenSSL-3. Unfortunately all older RubyInstaller are bound to OpenSSL-1.1 since OpenSSL-3 breaks the API on the ruby level, so that they will not be upgraded. Another option should be to exchange the libcrypto.dll and libssl.dll of RubyInstaller-3.2 manually to the newer OpenSSL-3.2 version. Did you try this? |
Ah, I only tried to swap |
|
Thank you for your efforts, everyone! Replacing:
now allows the gem to load (although with warnings): (I notice path separators in those paths are a mixed bunch of I do not intend to use JPEG-XL or OpenSlide (as such), so I hope this will still give me enough VIPS functionality to progress with what I am doing. I'm available for further testing, if you guys want to hammer this out. |
|
Turns out I merely did not have those two modules installed. After installing them by: the warnings are now gone and VIPS works! Thank you again! |
Greetings there,
Describe the bug
I am on Win10, RubyInstaller-devkit-3.2.2-1 and I must have some installation issue because even though
ruby-vipsis specified in myGemfileandbundlerruns and says everything is installed, the gem does not load:To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
The
vipsgem should load without error and provide access to using theVIPSlibrary.Desktop (please complete the following information):
Win10, RubyInstaller-devkit:
Additional context
The Windows-visible path
C:\Ruby32-x64\msys64\ucrt64\bin(inRUBY_DLL_PATHabove) corresponds to the same directory, as the RubyInstaller/pacman-visible/ucrt64/bin/directory.Sadly I do not see anywhere the name of the procedure that could not be found.
Any suggestions?
Thank you kindly in advance.
(My apologies: this feels a lot like #118 again, but I don't develop much on Windows, so I am not sure where to start.)
The text was updated successfully, but these errors were encountered: