On Mon, Apr 07, 2014 at 08:47:27PM -0300, Hisham wrote:
> I uploaded your rockspec as-is, but I didn't run the full build. I
> noticed your rocks depend on additional packages to build properly;
> you should look into specifying those in the external_dependencies
> block. It will make your rockspecs more robust and give your users
> better error messages and help them get the proper environment set up.
As with OpenCL for Lua, could you please upload the binary rock?
Unfortunately, specifying the run-time dependency of the tests (the
Lua plugin for GCC) is beyond the scope of external dependencies.
The Lua plugin for GCC may be used in three different setups:
1. Installed system-wide, either manually as root or using
apt-get install gcc-4.8-plugin-lua
(and in other distributions, if there is interest.)
In this case, the plugin is loaded using
gcc -fplugin=gcclua …
2. Installed in path accessible by the linker, ld.so,
export
LD_LIBRARY_PATH="${HOME}/projects/gcc-lua/gcc${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}"
In this case, the plugin is loaded using
gcc -fplugin=gcclua.so
3. Installed in an arbitrary path.
In this case, the plugin is loaded using
gcc -fplugin=$HOME/projects/gcc-lua/gcc/gcclua.so
Thanks,
Peter
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Luarocks-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
