View previous topic :: View next topic |
Author |
Message |
mao n00b
Joined: 22 Mar 2017 Posts: 43 Location: Poland
|
Posted: Fri Jan 05, 2018 12:23 pm Post subject: [SOLVED] matplotlib-1.4.3 emerge failure |
|
|
Hi again,
Today after syncing my local tree I ran Code: | emerge -aqvuD @world |
which in my case resulted in the following updates(downgrades):
sys-libs/gdbm-1.13-r2
dev-lang/python-2.7.14-r1
dev-lang/python-3.5.4-r1
dev-lang/python-3.4.5-r1
dev-lang/python-3.6.3-r1
dev-python/matplotlib-1.4.3 (downgraded from 2.0.2)
eventually, matplotlib-1.4.3 emerge failed:
Code: |
* Messages for package dev-python/matplotlib-1.4.3:
* ERROR: dev-python/matplotlib-1.4.3::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 124: Called src_compile
* environment, line 4136: Called distutils-r1_src_compile
* environment, line 1258: Called _distutils-r1_run_foreach_impl 'python_compile'
* environment, line 482: Called python_foreach_impl 'distutils-r1_run_phase' 'python_compile'
* environment, line 3591: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
* environment, line 2692: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
* environment, line 2690: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile'
* environment, line 829: Called distutils-r1_run_phase 'python_compile'
* environment, line 1251: Called python_compile
* environment, line 3120: Called wrap_setup 'distutils-r1_python_compile'
* environment, line 4976: Called distutils-r1_python_compile 'build' '--build-lib=/var/tmp/portage/dev-python/matplotlib-1.4.3/work/matplotlib-1.4.3-python2_7/build/build/lib'
* environment, line 1126: Called esetup.py 'build' 'build' '--build-lib=/var/tmp/portage/dev-python/matplotlib-1.4.3/work/matplotlib-1.4.3-python2_7/build/build/lib'
* environment, line 1738: Called die
* The specific snippet of code:
* "${@}" || die "${die_args[@]}";
*
* If you need support, post the output of `emerge --info '=dev-python/matplotlib-1.4.3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-python/matplotlib-1.4.3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-python/matplotlib-1.4.3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/matplotlib-1.4.3/temp/environment'.
* Working directory: '/var/tmp/portage/dev-python/matplotlib-1.4.3/work/matplotlib-1.4.3-python2_7'
* S: '/var/tmp/portage/dev-python/matplotlib-1.4.3/work/matplotlib-1.4.3'
|
I remember that in the past i had problem related to matplotlib-1.4.3 and PyQt ( https://forums.gentoo.org/viewtopic-t-1061048-highlight-matplotlib.html ), it was solved by unmasking later (unstable or live) version of matplotlib (which is aforementioned version 2.0.2). I shall try the same thing in this case, but problem of 1.4.3 version remains. I'm not sure whether there is a working configuration for users avoiding unstable packages in case of matplotlib.
Last edited by mao on Fri Jan 05, 2018 2:46 pm; edited 1 time in total |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30904 Location: here
|
Posted: Fri Jan 05, 2018 12:39 pm Post subject: |
|
|
You should post full build.log with wgetpaste _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
mao n00b
Joined: 22 Mar 2017 Posts: 43 Location: Poland
|
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30904 Location: here
|
Posted: Fri Jan 05, 2018 1:31 pm Post subject: |
|
|
Bug try this solution _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
mao n00b
Joined: 22 Mar 2017 Posts: 43 Location: Poland
|
Posted: Fri Jan 05, 2018 2:46 pm Post subject: |
|
|
Thanks, it worked for me. Marking as solved. |
|
Back to top |
|
|
ct85711 Veteran
Joined: 27 Sep 2005 Posts: 1791
|
Posted: Fri Jan 05, 2018 4:03 pm Post subject: |
|
|
In case you were wondering on why portage downgraded your matplotlib, is because the devs cleaned up some of the "old" ebuilds a little while ago (git log says about 6 hrs ago from now), leaving only 1.4.3, 2.1.0-r1, and the 9999 versions. So when your old version was removed, portage ended up picking the next version available, which ended up being a older version as the 2.1.0-r1 is marked as unstable. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|