Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=588941
--- Comment #27 from Toshio Ernie Kuratomi <a.badger(a)gmail.com> 2010-12-15 01:00:00
EST ---
Yeah, that's something I wanted to look into along with FHS compliance but
haven't had time. dmalcolm has this note in the spec file:
# Install the various support libraries as described at:
#
http://codespeak.net/pypy/dist/pypy/doc/getting-started-python.html#insta...
# which refers to a "PREFIX" found relative to the location of the binary.
# Given that the pypy binaries will be in /usr/bin, PREFIX can be
# "../share/pypy-1.2" relative to that directory, i.e. /usr/share/pypy-1.2
#
# Running "strace" on a built binary indicates that it searches within
# PREFIX/lib-python/modified-2.5.2
# not
# PREFIX/lib-python/modified.2.5.2
# as given on the above page, i.e. it uses '-' not '.'
But, at least with pypy-1.4, that doesn't work. pypy thinks the PREFIX is
/usr/bin/ when it would need to be /usr/share (or %{_libdir}/pypy-%{version} in
our case.)
You can either cd to /usr/share (or /usr/share/pypy-1.4... I'm not sure which
atm) or you can add /usr/share/pypy-1.4 to the PYTHONPATH in order to get pypy
to work. Really, though, we need to patch pypy to recognize the proper
directory.
--
Configure bugmail:
https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.