On Wed, 2007-01-31 at 23:53 +0100, Jens Peter Secher wrote: > On 1/30/07, Nicolas Cannasse <[EMAIL PROTECTED]> wrote:
> pkg-config is a Debian thing. It provides the right include path and compile > flags. No, yes. pkg-config is a *Red Hat* thing and it is frowned on by Debian. [As it should be, it's a heap of crap]. > > - Could you elaborate on -Wl,-rpath -Wl,/usr/lib/neko usage ? > > It hardcodes the library path /usr/lib/neko into the object files, which > removes the problems of setting LDPATH. Use of rpath is controversial for Debian. This rpath indicates neko libraries have been installed in the wrong location: Debian mandates /usr/lib, and that path is always searched for libraries so no rpath is needed. However many packages do not follow the Debian standard and put everything in /usr/lib/packagename-majorversion. Python for example does this (as does my own package Felix). This is because the Debian rules are archaic and do not make much sense for major systems, especially whole languages. Still .. IMHO rpath is a pretty bad solution, it makes code immobile. For example it is impossible to check a program built in a development directory because it will bind against the production (installed) libraries. IMHO a better solution is a script which sets LD_LIBRARY_PATH. Since Neko is a bytecode compiler, I would think that a script is a good idea anyhow. rpath is too brittle. What happens if Neko needs to be installed in Apache space? Web servers typically can't execute arbitrary programs for security reasons.. but the rpath will actually prevent such deployment. -- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net -- Neko : One VM to run them all (http://nekovm.org)
