New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warning: unmatched variable LUA_LIBDIR #1155
Comments
@doronbehar Last known working version is 3.2.1, right? Are you able to test this fetching from a specific LuaRocks commit? Looking at the commits between 3.2.1 and 3.3.1, I suspect 83126ba is the culprit, so testing revision 9499bb8 could answer the question. |
Oh right, I've reached the conclusion that I'll have to test everything with our build system because using I've tested the build of the failing package with Here's the log of the build with 3.2.1 which isn't considered to fail:
As for 9499bb8, I've tested it and the build failed the same way it failed with 3.3.1:
|
@doronbehar it's interesting that the 3.2.1 logs already show an empty |
It may also be a good idea to try to run |
While digging into our build system, I've discovered we use an automatically generated config file for every build of a Luarocks package. It's content are here: Unfortunately, I couldn't find a way to get it's contents for the build of However, as for running the build with
It's likely that you'll notice trace messages from other programs due to the fact I used a general Nix debug flag - it causes our compiler wrappers for example to be more verbose. |
I see similar errors on both 3.2.1:
and 3.3.1:
Looks like it was ignored in 3.2.1 but caught in 3.3.1... I even suspected if it was in issue in the |
I've traced down the issue to commit 3a3f2cb - building luv with luarocks built from 879c6ef which is right before 3a3f2cb doesn't fail. Here's the not failing build log with 879c6ef : https://gist.github.com/856e78c672a2b0b8385b01116f62f77a And the failing build with commit 3a3f2cb : https://gist.github.com/406902127e91cf02a582f4906205d4b3 |
@doronbehar Super interesting! Thank you for digging down to the specific commit! What's most interesting about this is that the central thing that this commit does is to add error checking: 3a3f2cb#diff-09933fcfab73d4a2d7c8ea3a9dad2ac7R446-R460 This means that an error was already happening before, but it was just not being caught and the process succeeded. The not-failing log in 879c6ef does include this:
I'll keep looking into this! |
Oh please I don't think you should dig too much into this. Apparently @ArdaXi has just confirmed that if we update |
Oh nice! This means that the new LuaRocks is catching the error correctly (whereas the previous one didn't) and whatever was causing the error was fixed in the latest version of the dependency. Mystery solved, then, happy to close this one! Thank you for all the debugging and detailed feedback! |
On NixOS, since 3.3.1 was released, we are having an issue with a certain cmake build. The package we are failing to install is https://github.com/luvit/luv. Here's the issue open on our end: NixOS/nixpkgs#79870 However, if from
luarocks
' repo, inmaster
I runluarocks --tree=test-luv install luv
the build doesn't fail, yet the warning message:And also Cmake reports this variable as empty:
It's likely that we'll need to update something in our build infrastructure, so I'm trying to figure out what it is and the meaning of this warning. Help will be appreciated.
The text was updated successfully, but these errors were encountered: