How to use 64-bit python on Solaris 10

[Roger Williams]

Could a Solaris guru please explain how the 64-bit Python installed with the
SUNWPython package on Solaris 10 is meant to be used?

The python binaries that are installed with that package do not seem to follow
Sun's "hard link to /usr/lib/isaexec" convention (as described in the Solaris
64-bit Developer’s Guide).

The python binary in /usr/bin is 32-bit. There is nothing in /usr/bin/sparcv7.
There are two individual (and identical) files in /usr/bin/sparcv9, viz

# ls -li /usr/bin | grep -i python
10117 lrwxrwxrwx 1 root root 9 Jul 3 2008 python -> python2.4
10124 -rwxr-xr-x 1 root bin 4872 Feb 1 2007 python2.4

# ls -li /usr/bin/sparcv7 | grep -i python

# ls -li /usr/bin/sparcv9 | grep -i python
10125 -rwxr-xr-x 1 root bin 7000 Feb 1 2007 python
10126 -rwxr-xr-x 1 root bin 7000 Feb 1 2007 python2.4

How is the 64-bit python meant to be run? And, in particular, how can a 64-bit
version of Numpy be compiled with a straightforward

% python setup.py build
# python setup.py install

Doing this on a Solaris 10 machine produces only 32-bit Numpy components. I'd
like to have 64-bit python and extras by default.

# isainfo -kv
64-bit sparcv9 kernel modules

Any guidance appreciated. This stuff is not my forte.

Thanks,
Roger
--
Roger Williams, GNS Science, New Zealand : www.gns.cri.nz

[Roger Williams]

On Wed, 21 Apr 2010 13:54:43 +1200, Roger Williams
<R.Wil...@gns.cri.nz.nospam> wrote:

>Could a Solaris guru please explain how the 64-bit Python installed with the
>SUNWPython package on Solaris 10 is meant to be used?

Following up on my own posting.

No answers/replies at all. That's very disappointing. Where are the helpful
experts of yesteryear?

Some of the comments here seem to be all too true ...

http://news.slashdot.org/story/10/04/21/210224/Cox-Discontinues-Usenet-Starting-In-June

[John D Groenveld]

In article <0hmss5t3l0mc3gshr...@4ax.com>,
Roger Williams <R.Wil...@gns.cri.nz.nospam> wrote:
>% python setup.py build

My WAG:
$ env PATH=/usr/bin/sparcv9:/usr/bin::/usr/sbin:/usr/ccs/bin:/opt/SUNWspro/bin \
python setup.py build

I have very little experience with Python, but with Perl and Ruby
based applications, I use my own builds of those interpreters
rather than Sun's.

Good luck and happy hacking,
John
groe...@acm.org

[Richard B. Gilbert]

I've never installed Python! When I install Solaris I make it a point
to do the FULL install. If Python is part of the kit, it's installed.
Some of what I install I may never use. I've always believed that disk
space is cheaper than my time to install the system piecemeal!

If I ever NEEDED Python, I didn't know it.

[Roger Williams]

On Thu, 22 Apr 2010 21:17:32 -0400, "Richard B. Gilbert"
<rgilb...@comcast.net> wrote:

> When I install Solaris I make it a point
>to do the FULL install. If Python is part of the kit, it's installed.

Yes, but the thing is that the installation of Python (using the Sun package,
from a FULL install) puts only a 32-bit binary in the path (in /usr/bin) even
though the package also installs a 64-bit binary (in /usr/bin/sparcv9) and that
the installation of these two different binaries is not something that I
understand. Particulary given that this seems to be not as per Sun's documented
"hard link to /usr/lib/isaexec" convention.

So, if I want to use the 64-bit python version (and I want to compile and
install things like Numpy), what is the recommended way to do that? Is it really
kosher to amend PATH to include /usr/bin/sparcv9 at the beginning?

BTW, thanks for the reply posting! The thread is alive :-)