>> I know using ldconfig will do the trick but this requires root >> privilege, which is not always available for DB admin. Also some >> people don't want to add /usr/local/lib to ld.so.conf for a security >> reason. >> >> So customizing Makefile is better, I think. > > IMHO, this is the responsability of the application packager or the sys > admin to put libraries in a place where they can be loaded by applications. > > If people compile and install pgpool under /usr/local, and put the > related libraries here they know what they are doing and should be able > to either move the libraries or tweak their ld.so.conf. > > Hard-coding this path in the Makefile is, as you said, horrible. But > even trying to discover where the lib is to tweak the Makefile > dynamically using ./configure is out of our scope. > > The only thing we should do is to document that, and maybe explain how > to run make giving a custom library path if the pgpool installation > require it, ie: > > make SHLIB_LINK="-L/usr/local/lib -lpcp > - -Wl,-rpath,'/usr/local/lib',--enable-new-dtags"
Yes, I don't want to hard code this into Makefile either. Probanly putting it into Makefile as a comment is enough. (Along with alternative way you described) -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp _______________________________________________ Pgpool-hackers mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-hackers
