Greets. Since the RHEL 4 Update 4 release it appears as if man crashes with the following message: /usr/bin/gtbl: /usr/lib/nsr/libgcc_s.so.1: version `GCC_4.2.0' not found (required by /usr/lib/libst
I will check on my macines tomorrow (timezone = europe) but a server install is differeent as it adds storage nose functionality and more so its different than a client install the modifications coul
but a server install is differeent as it adds storage nose functionality and more so its different than a client install the modifications could be in the extra packages That's what I'm thinking. I d
I'm thinking this is a Networker 7.3.x issue. While shipping a libgcc runtime isn't exactly something I'm thrilled to think about, it's kind of expected for a closed source application trying to run
Well, this is definitely NOT the way to do it. By putting that line into /etc/ld.so.conf you will force ALL other applications to use THEIR library, and that can/will break other applications relyin
Dag Nygren wrote: The right way o do thisios of course setting the LD_LIBRARY_PATH environment variable to /usr/lib/nar before starting the networker parts. Unfortunately, it looks more complex than
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 syst
Author: Byron Servies <bservies AT PACANG DOT COM>
Date: Tue, 29 Aug 2006 20:10:23 -0700
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 onl
In regard to: Re: [Networker] libgcc_s.so.1 from legato 7.2.1 on RHEL4,...: 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