>>Or you can link the library under /usr/ucblib, but this seems cause
>>some dynamic-linking problem. If you take this way, you should set
>>the environment variable LD_LIBRARY_PATH every time you want to run
>If you are going to use the Berkeley libs you should use
>/usr/ucb/cc for compiling and linking so you are sure to
>get the right include and library files. You will not
>need to set the LD_LIBRARY_PATH either.
Even better, use the new -R switch to set the run-time libraries.
-R allows you to link against uninstalled libraries (with -L)
and then run with the "to-be-installed" location of the libraries.
THis has the added benefit of not needing the LD_LIBRARY_PATH
evironment variable, since the binary itself know where to look
for the libraries. Syntax for -R is just like -L.
Also, I've never had a problem with any clients I've built in ucb
mode with the sparcworks compiler, you just need to add
-I/usr/ucbinclude to you build.
Bob Campbell Student Assistant System Manager
High Altitude Observatory National Center for Atmospheric Research
***** "Precisely, around here "religion" means
home *|_o_o|\\ Apple vs. IBM, WP vs W4W,
brew *|. o.| || MickeySoft vs. The Free World,
| o |// X windows vs The Forces of Darkness."
====== - random net post