> LD_LIBRARY_PATH (or equivalent) will need to be manually set. Then, after > install, LD_LIBRARY_PATH (or equivalent) will need to be set to include > the installed parrot library directory for every process that invokes > parrot.
I think that is the business of the packagers, or the final users that want to install from sources, to configure with a directory where his system can find it, or to set environment variables, use ldconfig, or whatever. This is a common scenario with common solutions. Of course, there is always the risk of people installing in /usr/local/lib and not having that directory in the ldconfig paths and complain us. But every project in the world that use gnu autotools face the same risk and live with it. -- Salu2 _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
