Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 504202 - dev-python/matplotlib-1.3.1: virtualmake: the wrap_setup distutils-r1_python_compile failed
Summary: dev-python/matplotlib-1.3.1: virtualmake: the wrap_setup distutils-r1_python_...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
: 500526 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-11 13:22 UTC by Andrey Grozin
Modified: 2014-04-02 07:07 UTC (History)
0 users

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


Attachments
bzip2ed log (matplotlib-1.3.1.log.bz2,10.52 KB, application/octet-stream)
2014-03-11 13:24 UTC, Andrey Grozin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Grozin gentoo-dev 2014-03-11 13:22:08 UTC
* The ebuild phase 'compile' with pid 22067 appears to have left an orphan
 * process running in the background.
 * ERROR: dev-python/matplotlib-1.3.1::gentoo failed (compile phase):
 *   virtualmake: the wrap_setup distutils-r1_python_compile failed.
 * 
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 3909:  Called distutils-r1_src_compile
 *   environment, line 1376:  Called _distutils-r1_run_foreach_impl 'python_compile'
 *   environment, line  352:  Called python_parallel_foreach_impl 'distutils-r1_run_phase' 'python_compile'
 *   environment, line 3659:  Called multibuild_parallel_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
 *   environment, line 2784:  Called multibuild_foreach_variant '_multibuild_parallel' '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
 *   environment, line 2732:  Called _multibuild_run '_multibuild_parallel' '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
 *   environment, line 2730:  Called _multibuild_parallel '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
 *   environment, line 2775:  Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile'
 *   environment, line  823:  Called distutils-r1_run_phase 'python_compile'
 *   environment, line 1367:  Called python_compile
 *   environment, line 3187:  Called virtualmake
 *   environment, line 4612:  Called die
 * The specific snippet of code:
 *       [[ ${retval} -ne 0 ]] && die "${FUNCNAME}: the ${VIRTUALX_COMMAND} failed.";
Comment 1 Andrey Grozin gentoo-dev 2014-03-11 13:24:29 UTC
Created attachment 372380 [details]
bzip2ed log
Comment 2 Ian Delaney (RETIRED) gentoo-dev 2014-03-18 14:46:03 UTC
did fine here.


testuser@gentoo64 ~/cvsPortage/gentoo-x86/dev-python/matplotlib $ ebuild matplotlib-1.3.1.ebuild clean install

running install_scripts
 * python2_7: running distutils-r1_run_phase python_install_all
>>> Completed installing matplotlib-1.3.1 into /mnt/gen2/TmpDir/portage/dev-python/matplotlib-1.3.1/image/

and was in a chroot

~/cvsPortage/gentoo-x86/dev-python/matplotlib $ ls -ld /mnt/gen2/TmpDir/portage/dev-python/matplotlib-1.3.1/temp/build.log 
-rw-rw---- 1 testuser portage 3803567 Mar 18 22:28 /mnt/gen2/TmpDir/portage/dev-python/matplotlib-1.3.1/temp/build.log

could not replicate
Comment 3 Andrey Grozin gentoo-dev 2014-04-01 15:23:09 UTC
Today got the same failure on another computer, ~x86. USE flags of matplotlib-1.3.1 are: cairo doc gtk latex qt4 tk wxwidgets, python_targets: python2_7 python3_2.
What's interesting is that matplotlib-1.3.1 is already successfully installed on the same computer with the same USE flags. On 20.12.2013. Some change in some other package[s] makes it impossible to re-emerge it now.
On my ~amd64 notebook, I cannot emerge it now; I haven't emerged it in 2013.
Comment 4 Andrey Grozin gentoo-dev 2014-04-01 15:23:37 UTC
*** Bug 500526 has been marked as a duplicate of this bug. ***
Comment 5 Andrey Grozin gentoo-dev 2014-04-02 07:07:29 UTC
I found that wxpython was broken after an upgrade of wxGTK. Re-emerging wxpython has solved the problem.