Skip to content
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

LuaRocks 3.1.3 Windows Warning: Could not find a Lua 5.3 interpreter in your PATH #1058

Closed
kingoftheconnors opened this issue Jul 18, 2019 · 5 comments

Comments

@kingoftheconnors
Copy link

@kingoftheconnors kingoftheconnors commented Jul 18, 2019

I installed LuaRocks using install.bat. Whenever I run ANY luarocks command (including help commands) I get this warning:

Warning: Could not find a Lua 5.3 interpreter in your PATH. Modules may not install with the correct configurations. You may want to specify to the path prefix to your build of Lua 5.3 using --lua-dir

Despite that, installing dkjson and using luarocks show dkjson worked fine. From what I've seen, warnings should be heeded, so this warning is giving me the creeps.

And yes, C:\lua\bin is in my PATH variable.

@xpol
Copy link
Contributor

@xpol xpol commented Oct 28, 2019

Same issue here.
I use the standalone exe.

Run where lua got the follow:

C:\Users\xpoli\Workspace\.lua\bin\lua.exe

Run tree C:/Users/xpoli/Workspace/.lua /A /F got:

C:\USERS\XPOLI\WORKSPACE\.LUA
+---bin
|       lua.dll
|       lua.exe
|       luac.exe
|       luarocks-admin.exe
|       luarocks.exe
|       wlua.exe
|
+---include
|       lauxlib.h
|       lua.h
|       lua.hpp
|       luaconf.h
|       lualib.h
|
+---lib
|       lua.lib
|
\---share
    \---lua
        |   README.md
        |
        +---doc
        |       contents.html
        |       index.css
        |       logo.gif
        |       lua.1
        |       lua.css
        |       luac.1
        |       manual.css
        |       manual.html
        |       osi-certified-72x60.png
        |       readme.html
        |
        \---etc
                lua.ico
                lua_lang.ico

Run luarocks:

Warning: Could not find a Lua 5.3 interpreter in your PATH. Modules may not install with the correct configurations. You may want to specify the path prefix to your build of Lua 5.3 using --lua-dir

Usage: luarocks [-h] [--version] [--dev] [--server <server>]
...

@RussellHaley
Copy link

@RussellHaley RussellHaley commented Jan 7, 2020

Hi,

I get this error on 3.2.1 using the all-in-one executable with my WinLua installer. When I use 3.0.3, I do not see the issue.

C:\Users\russh\git\WinLua-Bin [master ≡]> luarocks
Warning: Could not find a Lua 5.3 interpreter in your PATH. Modules may not install with the correct configurations. You may want to specify the path prefix to your build of Lua 5.3 using --lua-dir

Usage: luarocks [-h] [--version] [--dev] [--server <server>]
       [--only-server <server>] [--only-sources <url>]
       [--namespace <namespace>] [--lua-dir <prefix>]
       [--lua-version <ver>] [--tree <tree>] [--local] [--global]
       [--verbose] [--timeout <seconds>] [<command>] ...

LuaRocks 3.2.1, the Lua package manager

luarocks - LuaRocks main command-line interface

<snip>

Configuration:
   Lua version: 5.3

   Configuration files:
      System  : C:/Program Files (x86)/WinLua/LuaRocks/config-5.3.lua (ok)
      User    : C:/Users/russh/AppData/Roaming/luarocks/config-5.3.lua (not
      found)

   Rocks trees in use:
      C:\Users\russh\AppData\Roaming/luarocks ("user")
      c:\program files (x86)\winlua\lua\5.3\ ("system")

C:\Users\russh\git\WinLua-Bin [master ≡]> cat "C:/Program Files (x86)/WinLua/LuaRocks/config-5.3.lua"
rocks_trees = {
    { name = [[user]],
         root    = home..[[/luarocks]],
    },
    { name = [[system]],
         root    = [[c:\program files (x86)\winlua\lua\5.3\]],
    },
}
variables = {
    MSVCRT = 'VCRUNTIME140',
    LUA_LIBDIR = [[C:\Program Files (x86)\WinLua\Lua\5.3\bin]],
    LUA_INCDIR = [[C:\Program Files (x86)\WinLua\Lua\5.3\include]],
    LUALIB = 'lua53.lib',
}
verbose = false   -- set to 'true' to enable verbose output
C:\Users\russh\git\WinLua-Bin [master ≡]> luarocks list
Warning: Could not find a Lua 5.3 interpreter in your PATH. Modules may not install with the correct configurations. You may want to specify the path prefix to your build of Lua 5.3 using --lua-dir

Rocks installed for Lua 5.3
---------------------------

chronos
   0.2-4 (installed) - c:/program files (x86)/winlua/lua/5.3/lib/luarocks/rocks-5.3

dkjson
   2.5-2 (installed) - c:/program files (x86)/winlua/lua/5.3/lib/luarocks/rocks-5.3

I downloaded and installed 3.0.3 and copied the files into the luarocks installed directory. In the same powershell window, I then ran luarocks and do not get the error:

C:\Users\russh\git\WinLua-Bin [master ≡]> luarocks list

Rocks installed for Lua 5.3
---------------------------

chronos
   0.2-4 (installed) - c:/program files (x86)/winlua/lua/5.3/lib/luarocks/rocks-5.3

dkjson
   2.5-2 (installed) - c:/program files (x86)/winlua/lua/5.3/lib/luarocks/rocks-5.3

luasocket
   3.0rc1-2 (installed) - c:/program files (x86)/winlua/lua/5.3/lib/luarocks/rocks-5.3

C:\Users\russh\git\WinLua-Bin [master ≡]> luarocks

LuaRocks 3.0.3, the Lua package manager

<snip>

CONFIGURATION
        Lua version: 5.3

        Configuration files:
                System  : C:/Program Files (x86)/WinLua/LuaRocks/config-5.3.lua (ok)
                User    : C:/Users/russh/AppData/Roaming/luarocks/config-5.3.lua (not found)

        Rocks trees in use:
                C:/Users/russh/AppData/Roaming/luarocks ("user")
                c:/program files (x86)/winlua/lua/5.3 ("system")

C:\Users\russh\git\WinLua-Bin [master ≡]>

Thanks LuaRocks Team!
Russ

@hishamhm
Copy link
Member

@hishamhm hishamhm commented Jan 7, 2020

@RussellHaley does the same issue happen with that 64-bit .exe based off master that I shared in the other issue? (it's http://hisham.hm/luarocks/luarocks-test-windows-64.zip if any one else wants to test too!)

@Zulsorai
Copy link

@Zulsorai Zulsorai commented Jan 8, 2020

I just tried this out quickly as I have been having similar issues and it seems to persist with the new executable.

@wxm1122
Copy link

@wxm1122 wxm1122 commented Jan 13, 2020

me too!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants