Re: remote XOpenDisplay in Solaris (SunOS 5.6)

["Jerry Miller" <gmiller at cs dot sunysb dot edu>]

----- Original Message -----
From: David Korn <dkorn@pixelpower.com>
To: 'Jerry Miller' <gmiller@cs.sunysb.edu>; <help-gcc@gnu.org>
Sent: Friday, February 23, 2001 1:03 PM
Subject: RE: remote XOpenDisplay in Solaris (SunOS 5.6)


>   I believe you can probably use the 'ldd' utility to find out which
shared
> objects an executable needs.  If not, 'man ld.so' might point you in the
> right direction.  As I said, though, I'm not expert with shared objects.

Except for the order in which they are listed, every GUI executable
I subjected to ldd (those that bomb opening a remote display and
those that don't) produced the same list:

        libXm.so.3 =>    /usr/lib/libXm.so.3
        libXt.so.4 =>    /usr/openwin/lib/libXt.so.4
        libX11.so.4 =>   /usr/openwin/lib/libX11.so.4
        libm.so.1 =>     /usr/lib/libm.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libSM.so.6 =>    /usr/openwin/lib/libSM.so.6
        libICE.so.6 =>   /usr/openwin/lib/libICE.so.6
        libXext.so.0 =>  /usr/openwin/lib/libXext.so.0
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2
        /usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1

Oh well - still no clues here!