| Summary: | metakit fails to install against python-2.3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Seemant Kulleen (RETIRED) <seemant> |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dberkholz, dolsen, stephen |
| Priority: | High | ||
| Version: | 1.4 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 33372 | ||
|
Description
Seemant Kulleen (RETIRED)
2003-12-05 17:45:31 UTC
I just re-emerged metakit-2.4.9.2-r1 on my system which now has python-2.3-r5 installed and it emerged just fine. I looked over the emerge output with the error and compared it to mine and it looks like the command line was truncated in the bug reporters case. The correct line is as follows: /bin/install -c Mk4py.so /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/python2.2/site-packages/Mk4py.so Perhaps there was a different reason for the failure than the metakit ebiuld. What is the output at the start of emerging metakit. Namely what is it detecting for your python install?
e.g. Here is mine:
big_squirt brian # ACCEPT_KEYWORDS="~x86" emerge metakit
Calculating dependencies ...done!
>>> emerge (1 of 1) dev-db/metakit-2.4.9.2-r1 to /
>>> md5 src_uri ;-) metakit-2.4.9.2.tar.gz
>>> Unpacking source...
>>> Unpacking metakit-2.4.9.2.tar.gz to /var/tmp/portage/metakit-2.4.9.2-r1/work
>>> Source unpacked.
python
tcltk
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for Python configuration... /usr/include/python2.2 and /usr/lib/python2.2/site-packages
Is it detecting both directories?
Sorry for my earlier ramblings, I'm overtired. I only have python-2.2.3-r5 installed. My brain only saw 2.3. Does python 2.3 not have a site-packages directory installed and registered? Fixed in CVS *** Bug 35326 has been marked as a duplicate of this bug. *** *** Bug 38372 has been marked as a duplicate of this bug. *** This bug is still present in stable. Please consider getting the fix into stable. Actually... looks like it's in ~x86 as well... dev-db/metakit-2.4.9.3 and metakit-2.4.9.2-r1 both trigger this problem: /bin/install -c .libs/libmk4.a /usr/tmp/portage/metakit-2.4.9.3/image//usr/lib/libmk4.a ranlib /usr/tmp/portage/metakit-2.4.9.3/image//usr/lib/libmk4.a chmod 644 /usr/tmp/portage/metakit-2.4.9.3/image//usr/lib/libmk4.a libtool: install: warning: remember to run `libtool --finish /usr/lib' /bin/sh ./libtool --mode=install /bin/install -c Mk4py.so /usr/tmp/portage/metakit-2.4.9.3/image//usr/lib/python2.3/site-packages /bin/install -c Mk4py.so /usr/tmp/portage/metakit-2.4.9.3/image//usr/lib/python2.3/site-packages /bin/install: cannot create regular file `/usr/tmp/portage/metakit-2.4.9.3/image//usr/lib/python2.3/site-packages': No such file or directory make: *** [install-python] Error 1 !!! ERROR: dev-db/metakit-2.4.9.3 failed. !!! Function src_install, Line 43, Exitcode 2 !!! (no error message) Similar for 2.4.9.2-r1. Oddly, /usr/tmp/portage/metakit-2.4.9.3/image/usr/lib/python2.2/site-packages exists. Actually, dev-lang/python-2.2 was re-emerged as part of a revdep-rebuild I did for openssl-0.9.7. Gonna re-emerge 2.3 which should fix it. I had the same error. I re-emerged python and then re-emerged metakit and it worked fine. emerging metakit failed with: Python.h - no such file or directory i linked /usr/include/python2.3 to python2.2 which fixed this. any other/better solutions for this? seems that configure didn't detect the right python version (but only got 2.3 installed?) got no problems with the install... |