On 10/04/2013 20:03, Phil Clayton wrote:
In Linux that basically means "not listed in /etc/ld.so.conf" so the simplest solution is to add your location there.
You're right, I should really do that. In fact, on Fedora, I would add the file /etc/ld.so.conf.d/polyml-${version}.conf that contains the libdir.
I think that will probably work on Debian as well and probably other Linux distros.
My idea with the polyc script was to try to make it easy for people familiar with C to be able to try out Poly/ML. Of course it may evolve beyond that but for the moment I want to keep it simple.
I misunderstood the motivation for polyc. I thought that it was to allow those without compiling/linking knowledge to easily build executables, i.e. to de-skill the process. Whilst such users may realize that
./configure --prefix <non-standard location>
requires
PATH=${PATH}:${bindir}
they would not realize that they need (assuming no super-user privileges)
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${libdir}
I just wonder how common that case is. I would expect that most people manage their own machines and have sufficient privileges to be able to install software to the standard locations. The easiest way to try something out is usually to use the package management system to install a package configured for the distro and with all the dependencies sorted out. Personally, I would avoid installing something unfamiliar to a non-standard location because of the possibility of it breaking in unexpected ways.
David