Git Product home page Git Product logo

Comments (9)

hishamhm avatar hishamhm commented on May 22, 2024

All references to lib/lua/5.1 are now configurable through the luarocks.cfg mechanisms.

from luarocks.

ildar avatar ildar commented on May 22, 2024

Sorry for the noise.
As an example of the fix, the right /etc/luarocks/config.lua for x86_64 platform would be:

rocks_servers = {
[[http://luarocks.org/repositories/rocks]]
}
rocks_trees = {
home..[[/.luarocks]],
{ root = /usr,
bin_dir = /usr/bin,
lib_dir = /usr/lib64/lua/5.1,
lua_dir = /usr/share/lua/5.1
}
}

Works for me.

from luarocks.

ildar avatar ildar commented on May 22, 2024

Though the fix is not complete:
when using --tree arg, LR doesn't look at rocks_trees and builds path with lib_modules_path, which is hardcoded to "/lib/lua/"..lua_version.
I filed FR: #83

Care to reopen?

from luarocks.

hishamhm avatar hishamhm commented on May 22, 2024

Yes, it uses lib_modules_path from cfg.lua, but that is overrideable in config.lua as well. I'll keep #83 as valid, but lib/lua/5.1 is not hardcoded (it's just an overrideable defult).

from luarocks.

ildar avatar ildar commented on May 22, 2024

Yes! exactly. Again, sorry for the noise.
Then the correct /etc/luarocks/config.lua for x86_64 platform would be:

rocks_servers = {
[[http://luarocks.org/repositories/rocks]]
}
rocks_trees = {
home..[[/.luarocks]],
[[/usr]]
}
lib_modules_path = "/lib64/lua/"..lua_version

Works for me, even with --tree option.

from luarocks.

qbarnes avatar qbarnes commented on May 22, 2024

I just started playing with luarocks a few days ago and hit this problem, so consider me a luarocks noob.

Your reply above using lib_modules_path certainly works for me, but when I first hit this problem a couple of days ago, I had thought the way to fix this was to change the definition of LUA_LIBDIR in the site_config.lua file from "/usr/lib" to "/usr/lib64". However, that approach didn't work. Hisham, could you comment on whether this approach should have worked or not?

from luarocks.

hishamhm avatar hishamhm commented on May 22, 2024

No, they are different things. LUA_LIBDIR is the place where the shared library of the Lua interpreter is supposed to be. lib_modules_path is the path fragment for where Lua modules written in C should be installed to.

from luarocks.

qbarnes avatar qbarnes commented on May 22, 2024

Sounds like (also) changing LUA_LIBDIR to "/usr/lib64" on x86_64 is still a correct thing to do; it just doesn't address this problem, right?

I think I follow your explanation. That's why this variable is called "LUA_LIBDIR" rather than something like "LUAROCKS_LIBDIR".

from luarocks.

hishamhm avatar hishamhm commented on May 22, 2024

Sounds like (also) changing LUA_LIBDIR to "/usr/lib64" on x86_64 is still a correct thing to do

If your liblua_.so_ is there, then yes.

from luarocks.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.