whatever reasons (NOT for me not trying) I could not find it, could not even
find the Rocks file itself, as it kept being pasted in tmp and then deleted.
That used to irritate me, then I learned that the thing to do is
'luarocks unpack MOD' , which expands the rock locally, and then go to
the directory and do 'luarocks make' to explicitly build it.
Which lay beyond my efforts of finding out obviously. I'd opt for a
brief
hint to that option to be displayed if things fail. Failure, even
for LuaRocks,
will just always happen so "less black box" would be a virtue, even
if one
hopes it's never needed. Especially this compile flag problem is of
course in
no way LuaRocks specific, it happens all the time with
package/module
managers. I'd be grateful for a one-liner in the error message to
start me
out, specifically on fixing flags any time. There will always be the
next
chaos after shared and 32/64 bit have been settled.
Henning