Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.stack.nl!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Sun, 7 Oct 2012 10:01:58 -0700 (PDT)
In-Reply-To: <mailman.1885.1349483106.27098.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=123.192.32.215; posting-account=5JdMBQoAAABHnS4mjpqEzxnmWtgiiVNw
References: <mailman.1885.1349483106.27098.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Problems building Python from hg trunk on Open SUSE
From: 88888 Dihedral <dihedral88888@googlemail.com>
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Message-ID: <mailman.1927.1349629321.27098.python-list@python.org>
Lines: 140
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:30927

Skip Montanaro=E6=96=BC 2012=E5=B9=B410=E6=9C=886=E6=97=A5=E6=98=9F=E6=9C=
=9F=E5=85=ADUTC+8=E4=B8=8A=E5=8D=888=E6=99=8225=E5=88=8606=E7=A7=92=E5=AF=
=AB=E9=81=93=EF=BC=9A
> I haven't messed around with Python 3 recently, so decided to give it
>=20
> a whirl again.  I cloned the trunk (cpython) and set about it.  This
>=20
> is on an OpenSUSE 12.1 system.  I configured like so:
>=20
>=20
>=20
>   ./configure --prefix=3D/home/skipm/.linux-local
>=20
>=20
>=20
> and ran the usual "make ; make install".
>=20
>=20
>=20
> I'm a bit perplexed about how it is installed.  Instead of installing
>=20
> shared objects in
>=20
>=20
>=20
>   /home/skipm/.linux-local/lib/python3.4/lib-dynload
>=20
>=20
>=20
> they were installed in
>=20
>=20
>=20
> /home/skipm/.linux-local/lib64/python3.4/lib-dynload
>=20
>=20
>=20
> (note the "lib64" vs. "lib").  This would be fine, except sys.path
>=20
> doesn't include the "lib64" version of this path:
>=20
>=20
>=20
> % PYTHONPATH=3D PYTHONSTARTUP=3D ~/.linux-local/bin/python3.4 -S
>=20
> Could not find platform dependent libraries <exec_prefix>
>=20
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
>=20
> Python 3.4.0a0 (default:26200f535296, Oct  3 2012, 12:48:07)
>=20
> [GCC 4.4.6 [TWW]] on linux
>=20
> >>> import sys
>=20
> >>> sys.path
>=20
> ['', '', '/home/skipm/.linux-local/lib/python34.zip',
>=20
> '/home/skipm/.linux-local/lib/python3.4/',
>=20
> '/home/skipm/.linux-local/lib/python3.4/plat-linux',
>=20
> '/home/skipm/.linux-local/lib/lib-dynload']
>=20
>=20
>=20
> I see the message about setting PYTHONHOME.  (That happens to be bad
>=20
> advice as sys.prefix and sys.exec_prefix are identical in this case.)
>=20
> What I don't understand is why directories containing "lib64" are not
>=20
> in sys.path by default, given that that's where "make install" put
>=20
> things.
>=20
>=20
>=20
> GCC is as delivered by The Written Word.  (This is a work computer.
>=20
> The powers that be settled on TWW awhile ago for packaging all open
>=20
> source software we use on Linux and Solaris, thus removing a headache
>=20
> from our support staff.)  It is:
>=20
>=20
>=20
> % gcc --version
>=20
> gcc (GCC) 4.4.6 [TWW]
>=20
> Copyright (C) 2010 Free Software Foundation, Inc.
>=20
> This is free software; see the source for copying conditions.  There is N=
O
>=20
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOS=
E.
>=20
>=20
>=20
> The architecture looks like this:
>=20
>=20
>=20
> % uname -a
>=20
> Linux udesktop264 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45
>=20
> UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux
>=20
>=20
>=20
> I don't see anything in the output of "./configure --help" which
>=20
> relates to 64-bit install directories, though I do see some lines in
>=20
> config.log about guessing the architecture.  Some cursory googling
>=20
> didn't turn up any promising web pages, and I didn't find anything in
>=20
> the various documentation files in the repo related to building
>=20
> Python.
>=20
>=20
>=20
> Any suggestions about how to resolve this would be appreciated.
>=20
>=20
>=20
> Thx,
>=20
>=20
>=20
> Skip

I am waiting for JYTHON and IRON PYTHON to be upgraded.