Justin Walker on Tue, 29 Mar 2005 04:19:27 +0200

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Building on Solaris

Hi, all,

A question with, I hope, an obvious answer: I am helping someone build Pari on a Solaris box, remotely (I don't have access, so the communication path uses email). The configure and build phases seem to go without complaint, but when he tries to run this:

tree1:~/pari-2.2.9.alpha> ./gp
ld.so.1: ./gp: fatal: libgcc_s.so.1: open failed: No such file or directory

tree1:~/pari-2.2.9.alpha> ldd gp
libpari-2.2.so.9 => /afs/ir.stanford.edu/users/b/e/benbru/pari-2.2\
        libX11.so.6.1 =>         /usr/pubsw/X11R6/lib/libX11.so.6.1
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libm.so.1 =>     /usr/lib/libm.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libgcc_s.so.1 =>         (file not found)
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libgcc_s.so.1 =>         /usr/pubsw/lib/libgcc_s.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2

I see that libgcc_s.so.1 is referenced twice in this output. The first time, it is not found; the second time it is. I suspect this is because it is referenced in two different ways, but I don't know how to check this (not knowing much about 'ldd').

Can someone shed a little light?



Justin C. Walker, Curmudgeon-At-Large  *
Institute for General Semantics        |    Men are from Earth.
                                       |    Women are from Earth.
                                       |       Deal with it.