In regard to: Re: [Networker] libgcc_s.so.1 from legato 7.2.1 on RHEL4,...:

On Aug 29, 2006, at 5:22 PM, Lars Hecking wrote:

I don't do much with C, but as a guess it sounds like Legato/EMC should
be linking their dynamic libs with an rpath set to avoid the need to put
the path into the system config.

Yes, this is the only correct solution for this situation. Use -rpath
or LD_RUN_PATH at compile time. Modifying ld.so.conf smacks of the bad
habit of many Windoze software installers to replace system dlls with
their own (and break other software in the process).

I disagree.  The only correct solution is to fire the engineer(s) that
came up with this "solution" and hire someone with more than 2 active
neurons.

Understanding the linker and the loader on the platforms they support
has never been a strong point for Legato (and apparently EMC) engineers.
They've made horrible mistakes in that regard since the early days of
the product.  This one is just more obvious than others.

I agree with Lars that -rpath or LD_RUN_PATH is a better option in this
case than the one EMC chose or LD_LIBRARY_PATH, but I'm quite
surprised that no one has even suggested static linking.

Tim
--
Tim Mooney                                           Tim.Mooney AT ndsu DOT edu
Information Technology Services                      (701) 231-1076 (Voice)
Room 242-J6, IACC Building                           (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER