Please sign in to comment.
lua: install a dylib rather than a static liblua.
Although other loadable lua modules (such as those from luarocks) should not link against even a dynamic liblua and tie themselves to a particular release and runtime (e.g. breaking luajit capability): Having a statically linked non-pic liblua in the lua binary can and does cause hard to track memory allocation failure aborts due to some minutae of the way '-bundle -undefined dynamic_lookup' objects dlopened by the interpreter interact with the symbols resolved in the static binary. The solution is to always build and install liblua.dylib. It appears that this issue is confined to Snow Leopard and/or the version of gcc it ships with. This thread on the lua list contains the explanation and patch: http://lua-users.org/lists/lua-l/2009-10/msg00145.html Signed-off-by: Adam Vandenberg <email@example.com>
- Loading branch information...