*This message was transferred with a trial version of CommuniGate(tm) Pro*
Solution found:
I ended up using crle to add to the default library path:
# crle -u -l /usr/local/lib
Following great advice on this list (thanks all) I had tried using
LDFLAGS=-R/usr/local/lib, LD_LIBRARY_PATH
and
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hi all,
Having trouble with a solaris 8 compile of amanda 2.4.4 on sparc hardware.
I've compile amanda successfully before on the same platform, but cannot
work out what I'm doing wrong.
The problem manifests when I run
Jim
where's libgcc_s.so.1 ??? in /usr/local/lib ?
if it is then you'll have to include that in the LD_LIBRARY_PATH. This a
a runtime path (like $PATH, $MANPATH etc) that is used by Solaris to
search for libs during execution.
--
Martin Hepworth
Senior Systems Administrator
Solid State Logic
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Peter,
The problem manifests when I run amcheck:
ld.so.1: /usr/local/sbin/amcheck: fatal: libgcc_s.so.1: open failed: No
such
file or directory
what does ldd /usr/local/sbin/amcheck tells you ?
# ldd
Hi Jim,
Jim Mozley wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Peter,
The problem manifests when I run amcheck:
ld.so.1: /usr/local/sbin/amcheck: fatal: libgcc_s.so.1: open failed: No
such file or directory
[..]
Allthough libgcc_s.so.1 is
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Peter,
The problem manifests when I run amcheck:
ld.so.1: /usr/local/sbin/amcheck: fatal: libgcc_s.so.1: open failed:
No
such file or directory
[..]
Allthough libgcc_s.so.1 is not found it is in
On Mon, 2003-06-23 at 07:50, Jim Mozley wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Peter,
The problem manifests when I run amcheck:
ld.so.1: /usr/local/sbin/amcheck: fatal: libgcc_s.so.1: open failed:
No
such file or directory
[..]
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Jim,
I may have missed some of the things already tried, but I was wondering
if the logged in user also has the LD_LIBRARY_PATH set accurately?
Seems that has gotten me once or twice.
Has got me before too.
However,
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Jon,
The line below, quoted from one of your earlier messages, should make the
setting of LD_LIBRARY_PATH superfluous.
CFLAGS=-L/usr/local/lib -L/usr/lib LDFLAGS=-R/usr/local/lib
Both are ld(1) options and could be
if it is then you'll have to include that in the LD_LIBRARY_PATH. This a
a runtime path (like $PATH, $MANPATH etc) that is used by Solaris to
search for libs during execution.
The right way is to use -R during linking instead of LD_LIBRARY_PATH
10 matches
Mail list logo
