Problem building 64-bit python 2.6.2 on Solaris 10

[John Center]

On May 28, 6:03 pm, "Martin v. Löwis" <mar... at v.loewis.de> wrote:
> > I think the problem is it should be built with v9.S for 64-bit, not
> > v8.S.  Is that correct?  If so, how do I get it to use the right one?
>
> The Solaris dynamic loader can't find it. Set LD_LIBRARY_PATH or
> LD_RUN_PATH appropriately, or use crle(8).
>
> Regards,
> Martin

Hi Martin,

I'm not sure I understand.  It appears that cc is compiling the wrong
module, v8.S.  It should be compiling v9.S.  The errors are being
reported by fbe, the Sun Studio assembler, not ld.  I think there must
be a place to specify which I want to use, but I don't understand the
python build environment well enough to know where to do it.

You may be right about the first error.  It's being reported by ld,
but -L/opt/openssl/lib/sparcv9 & -R/opt/openssl/lib/sparcv9 are being
passed to cc.  It is able to find -lssl & -lcrypto, but I think python
itself doesn't use the openssl libraries.  Since I see the chain
"ld.so.1: python: fatal: libssl.so.0.9.8: open failed: No such file or
directory", which I think means python itself doesn't know where they
are at.  I checked python & libpython.so with ldd & neither uses
libssl.so.  It seems to me there should be another way to tell python
where to find it to build the module.  Does this make sense?

Thanks for your help.

    -John