On 01/19/2010 01:50 PM, nwat...@symcor.com wrote: > I've compiled cfengine on solaris with some libs in a custom location. > When I run cf it fails unless I set LD_LIBRARY_PATH to point to the custom > > libs. Is there a way to build the cf binaries with a built in default > library search path?
Isn't that more of an issue for the runtime/dynamic linker to solve, not Cfengine? I'm fuzzy on compiling and Solaris in general, but I see your options as either: - Compile static Cfengine binaries - Configure the runtime linking environment to include your custom location (see crle(1)) (this should be analogous to /etc/ld.so.conf on Linux) whar...@cds3 $ crle Default configuration file (/var/ld/ld.config) not found Default Library Path (ELF): /usr/lib (system default) Trusted Directories (ELF): /usr/lib/secure (system default) whar...@cds3 $ crle -64 Default configuration file (/var/ld/64/ld.config) not found Default Library Path (ELF): /usr/lib/64 (system default) Trusted Directories (ELF): /usr/lib/secure/64 (system default) -- /* Wes Hardin */ _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
