econf fails when app-pda/libopensync-0.22 was tried to emerge. The output is below. Reproducible: Always Steps to Reproduce: 1.emerge libopensync 2. 3. Actual Results: checking for Python include path... /usr/local/include/python2.5 checking for Python library path... configure: error: cannot find Python library path !!! Please attach the following file when seeking support: !!! /tmp/portage/app-pda/libopensync-0.22/work/libopensync-0.22/config.log * * ERROR: app-pda/libopensync-0.22 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2188: Called econf '--enable-engine' '--enable-tools' '--enable-python' '--enable-debug' '--enable-tracing' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/tmp/portage/app-pda/libopensync-0.22/temp/build.log'. * The ebuild environment file is located at '/tmp/portage/app-pda/libopensync-0.22/temp/environment'. * Expected Results: libopensync should build and install
Created attachment 201361 [details] ebuild environment
Created attachment 201405 [details] emerge --info
Created attachment 201413 [details] build log
Did you recently install python 2.6?
(In reply to comment #4) > Did you recently install python 2.6? > When this problem first started I had Python 2.5 (as stated); I have since updated to 2.6 and I still have the issue.
Ok, two things: use "eselect python" to check if 2.6 is selected as default and set it to that if it isn't run python-updater That might fix it - please report back.
(In reply to comment #6) > Ok, two things: > use "eselect python" to check if 2.6 is selected as default and set it to that > if it isn't > > run python-updater > > That might fix it - please report back. > I have a similar issue : during configure phase of libopensync 0.22 I get : checking for Python library path... find: `/usr/lib/python/config/': No such file or directory find: `/usr/lib/python/': No such file or directory and then it hangs , anyway I didn't try to wait and see what happens I recently upgraded to 2.6 , eselect python says 2.6 is selected and the problem happened while I was running python-updater
(In reply to comment #7) > I have a similar issue : during configure phase of libopensync 0.22 > I get : > checking for Python library path... find: `/usr/lib/python/config/': No such > file or directory > find: `/usr/lib/python/': No such file or directory > > > and then it hangs , anyway I didn't try to wait and see what happens waiting some minutes makes the configure script find the correct path : /usr/lib . Should I report the fact that it hangs for some minute as a separate bug or it's not a bug at all ?
It is fine for me, configure: error: cannot find Python library path !!! Please attach the following file when seeking support: !!! /tmp/portage/app-pda/libopensync-0.22/work/libopensync-0.22/config.log * * ERROR: app-pda/libopensync-0.22 failed. Reopen bug if you can still reproduce it
(In reply to comment #9) Hangs for about five minutes on both x86 and arm, but then seems to work fine. Not a major issue for me.
(In reply to comment #10) If it hangs for that long, it is probably from the wildly corrupt code in several packages' configure scripts with does something akin to this: :; find /usr/ -type f -name libpython2.6.* -print The python eclasses should look for that idiom in configure scripts and fix it; the ebuilds/eclasses know where the python lib is, so it can patch the configure scripts to know as well.
(In reply to comment #11) > (In reply to comment #10) > > If it hangs for that long, it is probably from the wildly corrupt code in > several packages' configure scripts with does something akin to this: > > :; find /usr/ -type f -name libpython2.6.* -print I'm still seeing this behaviour. I just synced, emerged world, revdep-rebuild, ran python-updater (which did lots, funny since I haven't upgraded python in months), and the behaviour is still the same: >>> Emerging (1 of 4) app-pda/libopensync-0.22 [snip] configure: Checking to see if we can build Python bindings checking for a Python interpreter with version >= 2.2... python checking for python... /usr/bin/python checking for python version... 2.6 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.6/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.6/site-packages checking for headers required to compile python extensions... found checking for swig... /usr/bin/swig checking for SWIG version... 2.0.0 configure: WARNING: SWIG version >= 1.3.17 is required. You have 2.0.0. You should look at http://www.swig.org checking for Python include path... /usr/include/python2.6 checking for Python library path... find: `/usr/lib/python/config/': No such file or directory find: `/usr/lib/python/': No such file or directory find: `/usr/games/bin': Permission denied find: `/usr/share/config': Permission denied find: `/usr/share/games': Permission denied find: `/usr/portage/packages/sys-apps': Permission denied /usr/lib/openoffice/basis3.2/program checking python extra libraries... configure: error: Building python explicitly requested, but can't build python bindings anyone interested in the build logs, and my emerge --info?
Created attachment 249901 [details, diff] bad patch to ignore SWIG version test Sorry for the double post, but it appears to be SWIG_LIB that's causing it to barf. The ./configure comments say swig lib >=1.3.17 is required, but the script tests for =1.3.17. Which is correct? Because of this, SWIG_LIB isn't set, and later if test x$SWIG_LIB = x; then have_python=no ... makes it exit. This patch (although completely wrong because I essentially ignoring the SWIG version test) fixes it for me, and compiles cleanly. different bug? worth fixing properly?
Please reopen this bug :) It stops libopensync-0.22 installing on recent Gentoo installations. The "find" command needs to be fixed because it can find openoffice directories in /usr instead, and the swig version test needs to be fixed. thanks :)
Reopening...
*** This bug has been marked as a duplicate of bug 328691 ***
