This is on RHEL 3 AS (Taroon update 5) on a dual
processor x86_64 machine

Attempting to build the RPM from Python.org fails with
a very non-descript error message:

+ mv -f idle idle2.4
+ echo '#!/usr/bin/env python2.4'
+ echo 'import os, sys'
+ echo 'os.execvp("/usr/bin/python2.4",
["/usr/bin/python2.4",
"/usr/lib/python2.4/idlelib/idle.py"] + sys.argv[1:])'
+ echo 'print "Failed to exec Idle"'
+ echo 'sys.exit(1)'
+ chmod 755 /var/tmp/python2.4-2.4.1-root/usr/bin/idle2.4
+ cp -a Tools
/var/tmp/python2.4-2.4.1-root/usr/lib64/python2.4
+ rm -f mainpkg.files
+ find
/var/tmp/python2.4-2.4.1-root/usr/lib64/python2.4/lib-dynload
-type f
+ sed 's|^/var/tmp/python2.4-2.4.1-root|/|'
+ grep -v -e '_tkinter.so$'
error: Bad exit status from /var/tmp/rpm-tmp.97009
(%install)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.97009 (%install)


So, thinking that it might be something related to
tkinter and idel, I tried not building those, but it
still fails to complete.  It appears that the problem
is that nothing is getting put in /usr/lib64 and
everything is getting put in /usr/lib.

Attempts were made at hacking the spec file to pass
--libdir=/usr/lib64 --exec-prefix=/usr to configure and
still have the problem that it doesn't put anything in
/usr/lib64 even though the spec file, and common logic,
would expect there to be files in /usr/lib64.

I was able to compile Python 2.4 just fine on the
machine and install it, but still it did not have
anything in /usr/lib64/python2.4, which is where the
architecture specific files should be.

Logged In: YES 
user_id=33168

Sean, do you have any insight into this issue?

Logged In: YES 
user_id=81797

This is a duplicate of bug 1294959
(https://sourceforge.net/tracker/?group_id=5470&atid=105470&func=detail&aid=1294959),
which I opened about a month ago.  That bug includes patches
from Red Hat which make it able to build the /usr/lib64
code.  I believe the above bug covers the details, if it
does not, let me know and I'll update it there.

The short form is that the Python build process doesn't have
any way to build for /usr/lib64 without hacking the code,
unless I'm missing something.

I was hoping the bug would lead to some discussion about how
best to approach this problem.  I guess I should post on
python-dev.

Logged In: YES 
user_id=33168

Yeah, you probably should post something...unless you want
to read about concurrency for ever until your mind
deadlocks...or is it live locks. ;-)