Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 591514 Details for
Bug 696012
app-admin/setools compile breaks with cython only using Python 2.7
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
build.log (text/x-log), 3.10 KB, created by
Richard H.
on 2019-10-01 20:42:23 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
Richard H.
Created:
2019-10-01 20:42:23 UTC
Size:
3.10 KB
patch
obsolete
> * Package: app-admin/setools-4.2.1 > * Repository: gentoo > * Maintainer: selinux@gentoo.org > * USE: abi_x86_32 elibc_glibc kernel_linux python_targets_python3_6 userland_GNU x86 > * FEATURES: network-sandbox preserve-libs sandbox selinux sesandbox userpriv usersandbox >!!! Failed to set new SELinux execution context. Is your current SELinux context allowed to run Portage? >>>> Unpacking source... >>>> Unpacking setools-4.2.1.tar.gz to /tmp/portage/app-admin/setools-4.2.1/work >>>> Source unpacked in /tmp/portage/app-admin/setools-4.2.1/work >!!! Failed to set new SELinux execution context. Is your current SELinux context allowed to run Portage? >>>> Preparing source in /tmp/portage/app-admin/setools-4.2.1/work/setools-4.2.1 ... > * Applying setools-4.2.2-remove-gui.patch ... > [ ok ] >>>> Source prepared. >!!! Failed to set new SELinux execution context. Is your current SELinux context allowed to run Portage? >>>> Configuring source in /tmp/portage/app-admin/setools-4.2.1/work/setools-4.2.1 ... >>>> Source configured. >!!! Failed to set new SELinux execution context. Is your current SELinux context allowed to run Portage? >>>> Compiling source in /tmp/portage/app-admin/setools-4.2.1/work/setools-4.2.1 ... > * python3_6: running distutils-r1_run_phase distutils-r1_python_compile >python3.6 setup.py build >Traceback (most recent call last): > File "setup.py", line 16, in <module> > from Cython.Build import cythonize >ModuleNotFoundError: No module named 'Cython' > * ERROR: app-admin/setools-4.2.1::gentoo failed (compile phase): > * (no error message) > * > * Call stack: > * ebuild.sh, line 125: Called src_compile > * environment, line 2629: Called distutils-r1_src_compile > * environment, line 816: Called _distutils-r1_run_foreach_impl 'distutils-r1_python_compile' > * environment, line 319: Called python_foreach_impl 'distutils-r1_run_phase' 'distutils-r1_python_compile' > * environment, line 2171: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' > * environment, line 1531: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'distutils-r1_python_compile' > * environment, line 1529: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'distutils-r1_python_compile' > * environment, line 534: Called distutils-r1_run_phase 'distutils-r1_python_compile' > * environment, line 807: Called distutils-r1_python_compile > * environment, line 677: Called esetup.py 'build' > * environment, line 1075: Called die > * The specific snippet of code: > * "${@}" || die "${die_args[@]}"; > * > * If you need support, post the output of `emerge --info '=app-admin/setools-4.2.1::gentoo'`, > * the complete build log and the output of `emerge -pqv '=app-admin/setools-4.2.1::gentoo'`. > * The complete build log is located at '/tmp/portage/app-admin/setools-4.2.1/temp/build.log'. > * The ebuild environment file is located at '/tmp/portage/app-admin/setools-4.2.1/temp/environment'. > * Working directory: '/tmp/portage/app-admin/setools-4.2.1/work/setools-4.2.1' > * S: '/tmp/portage/app-admin/setools-4.2.1/work/setools-4.2.1'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 696012
: 591514 |
591516