Re: libtool and 32/64-bit builds

[Albert Chin]

On Fri, Jul 26, 2002 at 11:19:59AM -0500, Albert Chin wrote:
> On Thu, Jul 25, 2002 at 06:53:38PM -0500, Bob Friesenhahn wrote:
> > On Thu, 25 Jul 2002, Albert Chin wrote:
> > 
> > > > What I make of it is that you didn't specify a -R option to find the
> > > > library, so ld.so looks in a system directory instead.  This has
> > > > nothing to do with 32 vs 64 bit.
> > >
> > > If -R was not included on the command-line, I should have received a
> > > '(file not found)' string in the ldd output. Consider the following:
> > 
> > Not necessarily so.  Since libz.so is a standard system library in
> > Solaris 9, it is found by default.  A -R is not required unless you
> > want it to use yours rather than the system's equivalent.
> 
> If that is the case, why did I get '(file not found)' when creating a
> 32-bit object file? I should have received the same result, regardless
> of creating a 32-bit or 64-bit object file.

The only thing that works for me is:
$ cc -xarch=v9 a.c -L/opt/TWWfsw/zlib11/lib/sparcv9 -lz
$ ldd a.out
        libz.so.2 =>     (file not found)
        libc.so.1 =>     /usr/lib/64/libc.so.1
        libdl.so.1 =>    /usr/lib/64/libdl.so.1
        /usr/platform/SUNW,Ultra-2/lib/sparcv9/libc_psr.so.1

So, I need to specify where the 64-bit libs are. Is there anything at
http://docs.sun.com that indicates "/64" or "/sparcv9" are appended by
the linker?

-- 
albert chin (address@hidden)