andrewcarver
commented
2 years ago I'm THINKING of raising this issue on Nokogiri's bug-tracker (as an [install] issue): the guy who runs Nokogiri also runs mini_portile, and it appears that the latest version of mini_portile2 (2.8.0) retains this same dubious bit of code.
On the other hand, I doubt they will be eager to help me to install Nokogiri v. 1.8.5, when they've got native-gem installation available for later versions of Nokogiri (>= 1.11.0).
So maybe the easiest fix for asciidoctor-bibliography would be to use a later version of Nokogiri...
ronaldtse
Hi team,
I wonder whether someone could corroborate, or else correct, my debugging of a problem I have installing asciidoctor-bibliography on a new Windows 10 machine. And I hope some could give me encouragement / advice, in either case.
(I'm quite weak in the ways that Linux folk 'make' do -- and even weaker on things Ruby; so, I need all the help I can get!)
My new machine's Ruby 3.1.1 install is via Chocolatey ( https://community.chocolatey.org/packages/ruby ). In pursuing the asciidoctor-bibliography install, I found it necessary also (or at least helpful) to install the Chocolatey package for MSYS2 ( https://community.chocolatey.org/packages/msys2 ).
At least from v. 0.10.0 onward, asciidoctor-bibliography depends on
nokogiri--~> 1.8.1, which entails the attempt to install, AND INDEED TO BUILD, its v. 1.8.5. In turn, nokogiri 1.8.5 depends onmini_portile2 (~> 2.3.0).In v. 2.3.0 of the latter gem, at around line 300 in mini_portile.rb, we see this:
def log_file(action)@log_files[action] ||=File.expand_path("#{action}.log", tmp_path).tap { |file|File.unlink(file) if File.exist?(file)}endJudging from a stack-trace I received several times, my build of nokogiri fails when the line in this function
File.unlink(file) if File.exist?(file)fails to unlink the 'configure.log' file, due to a Windows errno 'EACCES'.(Or, more fully, the top of the stack-trace:
C:/tools/ruby31/lib/ruby/gems/3.1.0/gems/mini_portile2-2.3.0/lib/mini_portile2/mini_portile.rb:302:in 'unlink'' Permission denied @ apply2files - C:/tools/ruby31/lib/ruby/gems/3.1.0/gems/nokogiri-1.8.5/ext/nokogiri/tmp/x86_64-w64-mingw32/ports/libiconv/1.15/configure.log (Errno::EACCES))I tried the first thing that comes to mind: to liberalise the permissions on the file itself; none of that solved the problem. But 'EACCES' doesn't pertain to that, necessarily; it has to do with an attempt to do anything to/with a file that is not permitted, by the nature or status of the file (e.g., trying to write to a read-only file). And in Windows that includes trying to delete (or "unlink") a file that's still open for any process (including the current one).
Which is why numerous posts say that if you're going to write Ruby in a Windows-compatible way, you have to be careful about this: e.g, you may decide to use Tempfile instead of File when you want to create (and then delete) a temporary-only file.
OK, let me just pose the question: Isn't this what's going on, in this mini_portile.rb which fails (right there at line 302) running on my Windows machine?
If we can agree on, or refute, that hypothesis, perhaps someone may be able to propose a fix to this fail.