lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


On Tue, Jul 24, 2018 at 03:01:28PM -0300, Hisham wrote:
> On 23 July 2018 at 23:45, Mike Schmitz <tmschmitz@gmail.com> wrote:
> > On Mon, Jul 23, 2018 at 05:03:05PM -0300, Hisham wrote:
> >> On 23 July 2018 at 14:12, Mike Schmitz <tmschmitz@gmail.com> wrote:
> >
> > --delete irrelevant
> >
> >> Instead of --lua-suffix you should use --lua-interpreter, in case
> >
> > This cued me to my issue. there was no --lua-interpreter or
> > --with-lua-interpreter in the configure file. I blew away the luarocks
> > dir and recloned it, and that issue no longer exists.
> >
> >> --lua-version isn't enough to autodetect it. (But given your setup, I
> >> believe `./configure --lua-version=5.[ver]` should be sufficient).
> >
> > indeed `./configure --lua-version=5.[ver]` was sufficient.
> >
> >> Thank you for the report, let's dig into this. Opening an issue on
> >> Github would be ideal, so we can track this without bothering lua-l.
> >
> > No need on that issue at least. User head space sufficiently adjusted.
> >
> > New issue though:
> >
> > mschmitz@ferrum:~/src/luarocks$ luarocks-5.3 search luaposix
> > /usr/bin/lua5.3: /usr/local/share/lua/5.3/luarocks/cfg.lua:179: attempt to call a nil value (field 'make_shallow_copy')
> > stack traceback:
> >         /usr/local/share/lua/5.3/luarocks/cfg.lua:179: in upvalue 'env_for_config_file'
> >         /usr/local/share/lua/5.3/luarocks/cfg.lua:209: in local 'load_config_file'
> >         /usr/local/share/lua/5.3/luarocks/cfg.lua:228: in main chunk
> >         [C]: in function 'require'
> >         /usr/local/bin/luarocks-5.3:5: in main chunk
> >         [C]: in ?
> > mschmitz@ferrum:~/src/luarocks$
> >
> > I will be happy to create an issue on github, if it will take more than
> > another minor adjustment to fix.
> 
> >From the stack trace, it reads like it is picking up modules from an
> older LuaRocks 2.x installation you may have around. Removing that and
> keeping only 3.0 will fix it.

That did it, thanx

Mike

Attachment: signature.asc
Description: PGP signature