New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MINGW32] mingw-w64-i686-lua51-luarocks installs broken config files #5928
Comments
I have just had occasion to look at the current 32-bit
This must at least be partly responsible for the errors I am seeing... |
SlySven
added a commit
to SlySven/MINGW-packages
that referenced
this issue
Jun 11, 2020
The elements in the `sed` expression are the wrong way around compared to those for the 64-bit install. It is my believe that this is the main part of the problem that I have described in: msys2#5928 Thus I believe that this will close msys2#5928 . Signed-off-by: Stephen Lyons <slysven@virginmedia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Immediately after installing the 32-Bit version of luarocks i.e.
mingw-w64-i686-lua51-luarocks
it is misconfigured as the output of theluarocks
command in a MINGW32 terminal shows:That error is indeed correct as there is not a
/mingw32/lib/luarocks/rocks
directory, but instead there is a/mingw32/lib/luarocks/rocks-5.1
one!As I am running on a 64-Bit system which does work (to allow Lua packages to be compiled/installed) I can compare the above with the output from the 64-Bit
mingw-w64-x86_64-lua51-luarocks
:Investigation of the differences between the two systems led me to the
/mingw32/share/lua/5.1/luarocks/site_config.lua
and it's counterpart/mingw64/share/lua/5.1/luarocks/site_config.lua
:If I manually edit that 32-Bit
site_config.lua
file to change them to correspond to the 64-Bit one so it becomes:The output from the plain
luarocks
command looks more promising:but the command to compile/install a package still fails:
the "Rocks trees in use:" still does not match the one for the 64-Bit case, and this leads to the (now being found where it wasn't before)
/mingw32/ect/luarocks/config-5.1.lua
file and it's/mingw64/ect/luarocks/config-5.1.lua
counterpart:Changing that Lua table to contain
root = [[C:/msys64/mingw32]]
seems to sort things out:Now this fixes the symptoms but does not identify the cause! I am not really expert enough to find where things are going wrong but I suspect that the internal execution flow through the Lua executable and interpreted scripts is not the same for the two systems - being that the 32-Bit one is probably inherited from the original MSYS/Mingw and the 64-Bit one has probably been bolted on afterwards!
I would note also that the two systems would seem to share a
~/.luarocks/config-5.1.lua
file - if it were to exist - on the other hand, since the system one seems to hold arocks_trees
lua table saying where the rocks and the compiled.dll
(packages) go for BOTH thesystem
and theuser
{used when the--local
optional argument is present} rocks case.It is not immediately obvious to me as what purpose the "User" Configuration file serves...? 😕
The text was updated successfully, but these errors were encountered: