You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This calls for a more thorough build setup of LuaJIT and special care about the search paths as the Lua environment used in ModScript should be completely independent from the system. This is will be fixed along with upgrading the LuaJIT version used, including considering to switch to openresty's LuaJIT.
The upgrade to openresty/luajit2 is done but the path are not fixed yet.
The cause of this issue is this: because we're building and bundling LuaJIT statically, C modules like luasocket need to be linked against our static LuaJIT library. Doing that works fine on linux but sadly on Windows it is harder or impossible (?) or would require more changes to the build system. This issue will be left as is but once the paths are fixed it will just fail to load the module because it's simply not here.
Here is a minimal example of this setup, works on Linux only : mkdir dep && make dep && make minimalcppluajit.zip
Probably related: apache/trafficserver#5158
This calls for a more thorough build setup of LuaJIT and special care about the search paths as the Lua environment used in ModScript should be completely independent from the system. This is will be fixed along with upgrading the LuaJIT version used, including considering to switch to openresty's LuaJIT.
package.path:
/home/user/.Rack2/plugins/ModScript/scripts/lib/?.lua;/home/user/.Rack2/plugins/ModScript/scripts/?.lua;/home/user/.Rack2/plugins/ModScript/scripts/lib/?/init.lua;./?.lua;/home/user/dev/ModScript/dep/share/luajit-2.0.5/?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/home/user/dev/ModScript/dep/share/lua/5.1/?.lua;/home/user/dev/ModScript/dep/share/lua/5.1/?/init.lua
package.cpath:
./?.so;/usr/local/lib/lua/5.1/?.so;/home/user/dev/ModScript/dep/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so
The text was updated successfully, but these errors were encountered: