[gentoo-user] Compiling uranium-2.6.0: Wrong python version, but...

[gentoo-user] Compiling uranium-2.6.0: Wrong python version, but...

[tuxic]

Hi,

compiling uranium failed here. From the output:
-- Using CURA_BINARY_DATA_DIRECTORY from set of environment variables...
CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find PythonInterp: Found unsuitable version "3.4.6", but required
  is at least "3.5.0" (found
  /var/tmp/portage/dev-python/uranium-2.6.0/temp/python3.4/bin/python)
Call Stack (most recent call first):
  /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:375 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake/Modules/FindPythonInterp.cmake:158 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  CMakeLists.txt:13 (find_package)


-- Configuring incomplete, errors occurred!
See also "/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build/CMakeFiles/CMakeOutput.log".
 * ERROR: dev-python/uranium-2.6.0::gentoo failed (configure phase):
 *   cmake failed
 * 
 * Call stack:
 *     ebuild.sh, line  124:  Called src_configure
 *   environment, line 4080:  Called cmake-utils_src_configure
 *   environment, line 1096:  Called die
 * The specific snippet of code:
 *       "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die "cmake failed";
 * 
 * If you need support, post the output of `emerge --info '=dev-python/uranium-2.6.0::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=dev-python/uranium-2.6.0::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/dev-python/uranium-2.6.0/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-python/uranium-2.6.0/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build'
 * S: '/var/tmp/portage/dev-python/uranium-2.6.0/work/Uranium-2.6.0'
[1]    15403 exit 1     emerge media-gfx/cura

But:
root>python --version
Python 3.5.4

eselect python list
Available Python interpreters, in order of preference:
  [1]   python3.5
  [2]   python3.4
  [3]   python2.7


How can I fix this?

Thanks a lot for any help in advance!
Cheers
Meino

Re: [gentoo-user] Compiling uranium-2.6.0: Wrong python version, but...

[Marc Joliet]

[-- Attachment #1: Type: text/plain, Size: 2701 bytes --]

Am Donnerstag, 19. Oktober 2017, 04:47:18 CEST schrieb tuxic@posteo.de:
> Hi,
> 
> compiling uranium failed here. From the output:
> -- Using CURA_BINARY_DATA_DIRECTORY from set of environment variables...
> CMake Error at
> /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
> Could NOT find PythonInterp: Found unsuitable version "3.4.6", but required
> is at least "3.5.0" (found
>   /var/tmp/portage/dev-python/uranium-2.6.0/temp/python3.4/bin/python)
> Call Stack (most recent call first):
>   /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:375
> (_FPHSA_FAILURE_MESSAGE)
> /usr/share/cmake/Modules/FindPythonInterp.cmake:158
> (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:13 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> See also
> "/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build/CMakeFi
> les/CMakeOutput.log". * ERROR: dev-python/uranium-2.6.0::gentoo failed
> (configure phase): *   cmake failed
>  *
>  * Call stack:
>  *     ebuild.sh, line  124:  Called src_configure
>  *   environment, line 4080:  Called cmake-utils_src_configure
>  *   environment, line 1096:  Called die
>  * The specific snippet of code:
>  *       "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die
> "cmake failed"; *
>  * If you need support, post the output of `emerge --info
> '=dev-python/uranium-2.6.0::gentoo'`, * the complete build log and the
> output of `emerge -pqv '=dev-python/uranium-2.6.0::gentoo'`. * The complete
> build log is located at
> '/var/tmp/portage/dev-python/uranium-2.6.0/temp/build.log'. * The ebuild
> environment file is located at
> '/var/tmp/portage/dev-python/uranium-2.6.0/temp/environment'. * Working
> directory:
> '/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build' * S:
> '/var/tmp/portage/dev-python/uranium-2.6.0/work/Uranium-2.6.0' [1]    15403
> exit 1     emerge media-gfx/cura
> 
> But:
> root>python --version
> Python 3.5.4
> 
> eselect python list
> Available Python interpreters, in order of preference:
>   [1]   python3.5
>   [2]   python3.4
>   [3]   python2.7
> 
> 
> How can I fix this?
> 
> Thanks a lot for any help in advance!
> Cheers
> Meino

Hi Meino,

what do $PYTHON_SINGLE_TARGET and $PYTHON_TARGETS look like on your system 
(check, e.g., the output of "emerge --info")?  Those determine what version of 
python the package actually uses.

In any case, I would file a bug that apparently Python 3.4 is not supported by 
that package anymore, so that it can be removed from the list of compatible 
versions.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Compiling uranium-2.6.0: Wrong python version, but...

[tuxic]

On 10/19 09:24, Marc Joliet wrote:
> Am Donnerstag, 19. Oktober 2017, 04:47:18 CEST schrieb tuxic@posteo.de:
> > Hi,
> > 
> > compiling uranium failed here. From the output:
> > -- Using CURA_BINARY_DATA_DIRECTORY from set of environment variables...
> > CMake Error at
> > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
> > Could NOT find PythonInterp: Found unsuitable version "3.4.6", but required
> > is at least "3.5.0" (found
> >   /var/tmp/portage/dev-python/uranium-2.6.0/temp/python3.4/bin/python)
> > Call Stack (most recent call first):
> >   /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:375
> > (_FPHSA_FAILURE_MESSAGE)
> > /usr/share/cmake/Modules/FindPythonInterp.cmake:158
> > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:13 (find_package)
> > 
> > 
> > -- Configuring incomplete, errors occurred!
> > See also
> > "/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build/CMakeFi
> > les/CMakeOutput.log". * ERROR: dev-python/uranium-2.6.0::gentoo failed
> > (configure phase): *   cmake failed
> >  *
> >  * Call stack:
> >  *     ebuild.sh, line  124:  Called src_configure
> >  *   environment, line 4080:  Called cmake-utils_src_configure
> >  *   environment, line 1096:  Called die
> >  * The specific snippet of code:
> >  *       "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die
> > "cmake failed"; *
> >  * If you need support, post the output of `emerge --info
> > '=dev-python/uranium-2.6.0::gentoo'`, * the complete build log and the
> > output of `emerge -pqv '=dev-python/uranium-2.6.0::gentoo'`. * The complete
> > build log is located at
> > '/var/tmp/portage/dev-python/uranium-2.6.0/temp/build.log'. * The ebuild
> > environment file is located at
> > '/var/tmp/portage/dev-python/uranium-2.6.0/temp/environment'. * Working
> > directory:
> > '/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build' * S:
> > '/var/tmp/portage/dev-python/uranium-2.6.0/work/Uranium-2.6.0' [1]    15403
> > exit 1     emerge media-gfx/cura
> > 
> > But:
> > root>python --version
> > Python 3.5.4
> > 
> > eselect python list
> > Available Python interpreters, in order of preference:
> >   [1]   python3.5
> >   [2]   python3.4
> >   [3]   python2.7
> > 
> > 
> > How can I fix this?
> > 
> > Thanks a lot for any help in advance!
> > Cheers
> > Meino
> 
> Hi Meino,
> 
> what do $PYTHON_SINGLE_TARGET and $PYTHON_TARGETS look like on your system 
> (check, e.g., the output of "emerge --info")?  Those determine what version of 
> python the package actually uses.
> 
> In any case, I would file a bug that apparently Python 3.4 is not supported by 
> that package anymore, so that it can be removed from the list of compatible 
> versions.
> 
> HTH
> -- 
> Marc Joliet
> --
> "People who think they know everything really annoy those of us who know we
> don't" - Bjarne Stroustrup

Hi Marc,

thanks for your reply ! :)

It is not set at all.
Is it possible to set that "locally" only fo rthe compilation
process. I fear, that I will screw up the whole system when
using make.conf for this purpose...

Cheers
Meino