[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Unpicking require
- From: Sean Conner <sean@...>
- Date: Sat, 27 Nov 2021 21:22:37 -0500
It was thus said that the Great Gavin Wraith once stated:
> On 2021-11-25 13:07, Roberto Ierusalimschy wrote:
> >When 'require' fails, its error message contains the names of all
> >files it tried to open. If there are no bugs there, these names should
> >be exactly the ones given to 'fopen':
> >>require 'XX.YY'
> >stdin:1: module 'XX.YY' not found:
> > no field package.preload['XX.YY']
> > no file '/usr/local/share/lua/5.4/XX/YY.lua'
> > no file '/usr/local/share/lua/5.4/XX/YY/init.lua'
> > [...]
> >Can't you use that to check whether your configuration is correct?
> Thanks. I had just got this issue sorted. But I have another. Dynamic
> loading of C modules causes a segmentation fault after the loaded code
> has run.
> local path, cpath in package
> print (path, cpath)
> local x = require "riscos"
> print (x.version)
I just noticed something---you have
local path, cpath in package
That's not legal Lua syntax that I'm aware of. Are you using a custom
version of Lua? Which version?