[ python-Bugs-1667877 ] Install fails with no error
SourceForge.net
noreply at sourceforge.net
Mon Feb 26 07:10:45 CET 2007
Bugs item #1667877, was opened at 2007-02-24 10:10
Message generated for change (Comment added) made by widgeteye
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1667877&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Installation
Group: None
>Status: Open
Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: larry (widgeteye)
Assigned to: Nobody/Anonymous (nobody)
Summary: Install fails with no error
Initial Comment:
When I built python 2.5 for linux I did the normal:
configure
make
make install
Everything went fine til the "make install" part. It dies with no
error.
just says "install failed" after this:
Compiling /usr/local/lib/python2.5/zipfile.py
That part built fine but the next part failed.
So what I did being the industrious fellow that I am I did:
make -n install > out
Took the out file and did:
sh out
That installed python without failure.
Now if I do "make install" everything works fine.
Weird eh?
----------------------------------------------------------------------
>Comment By: larry (widgeteye)
Date: 2007-02-26 00:10
Message:
Logged In: YES
user_id=402539
Originator: YES
I think you missed the point I was trying to make. When I say "works fine"
I mean
that after I installed python using the shell script, then I could run
"make install"
and it would complete the install using make without failure.
----------------------------------------------------------------------
Comment By: Martin v. Löwis (loewis)
Date: 2007-02-25 16:01
Message:
Logged In: YES
user_id=21627
Originator: NO
I'm not finding it weird that the shell script completed. I doubt it
"works fine", though. Instead, some command in it failed, but the shell
doesn't abort in this case - make would abort.
Typically, when byte-compilation fails, it is because you have a file
byte-compiled that has a syntax error in it. Scroll through the entire
compileall output to see what the actual problem is.
Tentatively closing this as "won't fix".
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1667877&group_id=5470
More information about the Python-bugs-list
mailing list