Re: Unpicking require

[Roberto Ierusalimschy <roberto@...>]

> Done that, but still no cigar. It could, of course, be an artefact of the
> RISC OS port of GCC and Unixlib. Make's dotty naming conventions have
> spawned some truly horrendous complications for C compilers in RISC OS
> which concern interchanging filename and extender. Thus Unix 'foo.c' =>
> RISC OS 'c.foo' or 'foo/c'.

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?

-- Roberto