Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 35168 - metakit fails to install against python-2.3
Summary: metakit fails to install against python-2.3
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
: 35326 38372 (view as bug list)
Depends on:
Blocks: 33372
  Show dependency tree
 
Reported: 2003-12-05 17:45 UTC by Seemant Kulleen (RETIRED)
Modified: 2004-07-16 17:03 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Seemant Kulleen (RETIRED) gentoo-dev 2003-12-05 17:45:31 UTC
image//usr/include
/bin/install -c -m 644 unix/../include/mk4.h /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/include/mk4.h
/bin/install -c -m 644 unix/../include/mk4.inl /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/include/mk4.inl
/bin/install -c -m 644 unix/../include/mk4str.h /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/include/mk4str.h
/bin/install -c -m 644 unix/../include/mk4str.inl /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/include/mk4str.inl
/bin/sh ./libtool --mode=install /bin/install -c libmk4.la /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib
/bin/install -c .libs/libmk4.so /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/libmk4.so
/bin/install -c .libs/libmk4.lai /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/libmk4.la
/bin/install -c .libs/libmk4.a /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/libmk4.a
ranlib /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/libmk4.a
chmod 644 /var/tmp/portage/metakit-2.4.9.2-r1/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 /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/python2.2/site-packages
/bin/install -c Mk4py.so /var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/python2.2/site-packages
/bin/install: cannot create regular file `/var/tmp/portage/metakit-2.4.9.2-r1/image//usr/lib/python2.2/site-packages': No such file or directory
make: *** [install-python] Error 1
Comment 1 Brian Dolbec (RETIRED) gentoo-dev 2003-12-06 12:05:37 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.
Comment 2 Brian Dolbec (RETIRED) gentoo-dev 2003-12-06 13:44:26 UTC
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?
Comment 3 Brian Dolbec (RETIRED) gentoo-dev 2003-12-06 22:28:30 UTC
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?
Comment 4 Bryan Østergaard (RETIRED) gentoo-dev 2003-12-07 18:47:17 UTC
Fixed in CVS
Comment 5 Bryan Østergaard (RETIRED) gentoo-dev 2003-12-09 08:30:20 UTC
*** Bug 35326 has been marked as a duplicate of this bug. ***
Comment 6 Mr. Bones. (RETIRED) gentoo-dev 2004-01-17 02:23:27 UTC
*** Bug 38372 has been marked as a duplicate of this bug. ***
Comment 7 Jeremy Huddleston (RETIRED) gentoo-dev 2004-02-07 17:36:02 UTC
This bug is still present in stable.  Please consider getting the fix into stable.
Comment 8 Jeremy Huddleston (RETIRED) gentoo-dev 2004-02-07 17:40:26 UTC
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.
Comment 9 Jeremy Huddleston (RETIRED) gentoo-dev 2004-02-07 17:58:43 UTC
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.
Comment 10 Matt Dew 2004-02-19 21:56:36 UTC
I had the same error. I re-emerged python and then re-emerged metakit and it worked fine.
Comment 11 Thomas K 2004-07-16 17:03:37 UTC
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...