Re: [gentoo-user] meson build woes
Sorry sorry sorry… Franz is right... Do not uninstall all python versions ! Hogren On 24/08/2020 11:39, Franz Fellner wrote: On Mo 24 Aug 2020 11:21:10 +0200, Hogren wrote: Maybe try to : - Unmerge all python and python-setuptools versions No, don't do that!!! Unmerging all python version will leave you with a non-working portage. portage is written in python. You can fix that but it requires some manual intervention... - Verify your package.use files. Run "grep -Ri 'python' /etc/portage/package.use/" and delete old files. - Run a "emerge --newuse --update --autounmask-write --deep --with-bdeps=y @world". This should be the first thing to check. package.use and probably also make.conf should be looked for PYTHON settings. Uncomment affected lines first (put the character # at the beginning) before deleting. The "--deep --newuse" emerge options should take care for the rest.
Re: [gentoo-user] meson build woes
On Mo 24 Aug 2020 11:21:10 +0200, Hogren wrote: > Maybe try to : > > - Unmerge all python and python-setuptools versions No, don't do that!!! Unmerging all python version will leave you with a non-working portage. portage is written in python. You can fix that but it requires some manual intervention... > - Verify your package.use files. Run "grep -Ri 'python' > /etc/portage/package.use/" and delete old files. > > - Run a "emerge --newuse --update --autounmask-write --deep > --with-bdeps=y @world". This should be the first thing to check. package.use and probably also make.conf should be looked for PYTHON settings. Uncomment affected lines first (put the character # at the beginning) before deleting. The "--deep --newuse" emerge options should take care for the rest.
Re: [gentoo-user] meson build woes
Hi,
In your logs, I saw that python 3.7 is executed.
And you wrote that python 3.6 is selected.
I had many problem with the python transition too. I have no simple
solution. I uninstalled many things for reinstall after.
Maybe try to :
- Unmerge all python and python-setuptools versions
- Verify your package.use files. Run "grep -Ri 'python'
/etc/portage/package.use/" and delete old files.
- Run a "emerge --newuse --update --autounmask-write --deep
--with-bdeps=y @world".
Hogren
On 23/08/2020 07:16, Paul Colquhoun wrote:
For the past month or so (since the recent Python version changes) I
haven't been able to get a full emerge update to complete.
The main culprit seems to be meson, but only because what looks like
an internal Python module, "setup.py", can't import 'setup' from
'setuptools'
All the remaining failures are either the same error, or dependencies
of packages that get the error.
I have been trying various combinations of which Python version is the
default and which versions are in the "PYTHON_TARGETS" variable, but
nothing seems to change much.
Rebuilding dev-python/setuptools didn't help either.
My google searches for the error message
"cannot import name 'setup' from 'setuptools'"
also haven't turned up anything that seemed relevent to my system
Does anyone have any suggestions on what I can try before I rebuild my
system from scratch?
The relevant section of the build log in included below, and the full
log is attached.
"eselect python list" tells me tjhat the default should be python3.6
###
* python3_7: running distutils-r1_run_phase distutils-r1_python_compile
python3.7 setup.py build -j 6
Traceback (most recent call last):
File "setup.py", line 24, in
from setuptools import setup
ImportError: cannot import name 'setup' from 'setuptools' (unknown
location)
* ERROR: dev-util/meson-0.54.2::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_compile
* environment, line 2949: Called distutils-r1_src_compile
* environment, line 1219: Called _distutils-r1_run_foreach_impl
'distutils-r1_python_compile'
* environment, line 447: Called python_foreach_impl
'distutils-r1_run_phase' 'distutils-r1_python_compile'
* environment, line 2557: Called multibuild_foreach_variant
'_python_multibuild_wrapper' 'distutils-r1_run_phase'
'distutils-r1_python_compile'
* environment, line 2056: Called _multibuild_run
'_python_multibuild_wrapper' 'distutils-r1_run_phase'
'distutils-r1_python_compile'
* environment, line 2054: Called _python_multibuild_wrapper
'distutils-r1_run_phase' 'distutils-r1_python_compile'
* environment, line 846: Called distutils-r1_run_phase
'distutils-r1_python_compile'
* environment, line 1210: Called distutils-r1_python_compile
* environment, line 1079: Called esetup.py 'build' '-j' '6'
* environment, line 1600: Called die
* The specific snippet of code:
* "${@}" || die "${die_args[@]}";
###
--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro
[gentoo-user] meson build woes
For the past month or so (since the recent Python version changes) I haven't
been able to
get a full emerge update to complete.
The main culprit seems to be meson, but only because what looks like an
internal Python
module, "setup.py", can't import 'setup' from 'setuptools'
All the remaining failures are either the same error, or dependencies of
packages that get
the error.
I have been trying various combinations of which Python version is the default
and which
versions are in the "PYTHON_TARGETS" variable, but nothing seems to change much.
Rebuilding dev-python/setuptools didn't help either.
My google searches for the error message
"cannot import name 'setup' from 'setuptools'"
also haven't turned up anything that seemed relevent to my system
Does anyone have any suggestions on what I can try before I rebuild my system
from
scratch?
The relevant section of the build log in included below, and the full log is
attached.
"eselect python list" tells me tjhat the default should be python3.6
#
##
* python3_7: running distutils-r1_run_phase distutils-r1_python_compile
python3.7 setup.py build -j 6
Traceback (most recent call last):
File "setup.py", line 24, in
from setuptools import setup
ImportError: cannot import name 'setup' from 'setuptools' (unknown location)
* ERROR: dev-util/meson-0.54.2::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_compile
* environment, line 2949: Called distutils-r1_src_compile
* environment, line 1219: Called _distutils-r1_run_foreach_impl 'distutils-
r1_python_compile'
* environment, line 447: Called python_foreach_impl
'distutils-r1_run_phase' 'distutils-
r1_python_compile'
* environment, line 2557: Called multibuild_foreach_variant
'_python_multibuild_wrapper' 'distutils-r1_run_phase'
'distutils-r1_python_compile'
* environment, line 2056: Called _multibuild_run
'_python_multibuild_wrapper' 'distutils-
r1_run_phase' 'distutils-r1_python_compile'
* environment, line 2054: Called _python_multibuild_wrapper
'distutils-r1_run_phase'
'distutils-r1_python_compile'
* environment, line 846: Called distutils-r1_run_phase
'distutils-r1_python_compile'
* environment, line 1210: Called distutils-r1_python_compile
* environment, line 1079: Called esetup.py 'build' '-j' '6'
* environment, line 1600: Called die
* The specific snippet of code:
* "${@}" || die "${die_args[@]}";
#
##
--
Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/
Asking for technical help in newsgroups? Read this first:
http://catb.org/~esr/faqs/smart-questions.html#intro
* Package:dev-util/meson-0.54.2
* Repository: gentoo
* Maintainer: flop...@gentoo.org willi...@gentoo.org
* USE:abi_x86_64 amd64 elibc_glibc kernel_linux
python_targets_python3_6 python_targets_python3_7 userland_GNU
* FEATURES: installsources network-sandbox preserve-libs sandbox userpriv
usersandbox
* Applying 0.54.2-multilib-clang.patch ...
[ ok ]
* python3_6: running distutils-r1_run_phase distutils-r1_python_compile
python3.6 setup.py build -j 6
running build
running build_py
creating
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/mtest.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/mesonmain.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/interpreterbase.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/msetup.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/msubprojects.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/depfile.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/munstable_coredata.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/mlog.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/mintro.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/envconfig.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/minit.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/coredata.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/mesonlib.py ->
/var/tmp/portage/dev-util/meson-0.54.2/work/meson-0.54.2-python3_6/lib/mesonbuild
copying mesonbuild/mparser.py
