1 |
On 10/19 09:24, Marc Joliet wrote: |
2 |
> Am Donnerstag, 19. Oktober 2017, 04:47:18 CEST schrieb tuxic@××××××.de: |
3 |
> > Hi, |
4 |
> > |
5 |
> > compiling uranium failed here. From the output: |
6 |
> > -- Using CURA_BINARY_DATA_DIRECTORY from set of environment variables... |
7 |
> > CMake Error at |
8 |
> > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:137 (message): |
9 |
> > Could NOT find PythonInterp: Found unsuitable version "3.4.6", but required |
10 |
> > is at least "3.5.0" (found |
11 |
> > /var/tmp/portage/dev-python/uranium-2.6.0/temp/python3.4/bin/python) |
12 |
> > Call Stack (most recent call first): |
13 |
> > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:375 |
14 |
> > (_FPHSA_FAILURE_MESSAGE) |
15 |
> > /usr/share/cmake/Modules/FindPythonInterp.cmake:158 |
16 |
> > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) CMakeLists.txt:13 (find_package) |
17 |
> > |
18 |
> > |
19 |
> > -- Configuring incomplete, errors occurred! |
20 |
> > See also |
21 |
> > "/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build/CMakeFi |
22 |
> > les/CMakeOutput.log". * ERROR: dev-python/uranium-2.6.0::gentoo failed |
23 |
> > (configure phase): * cmake failed |
24 |
> > * |
25 |
> > * Call stack: |
26 |
> > * ebuild.sh, line 124: Called src_configure |
27 |
> > * environment, line 4080: Called cmake-utils_src_configure |
28 |
> > * environment, line 1096: Called die |
29 |
> > * The specific snippet of code: |
30 |
> > * "${CMAKE_BINARY}" "${cmakeargs[@]}" "${CMAKE_USE_DIR}" || die |
31 |
> > "cmake failed"; * |
32 |
> > * If you need support, post the output of `emerge --info |
33 |
> > '=dev-python/uranium-2.6.0::gentoo'`, * the complete build log and the |
34 |
> > output of `emerge -pqv '=dev-python/uranium-2.6.0::gentoo'`. * The complete |
35 |
> > build log is located at |
36 |
> > '/var/tmp/portage/dev-python/uranium-2.6.0/temp/build.log'. * The ebuild |
37 |
> > environment file is located at |
38 |
> > '/var/tmp/portage/dev-python/uranium-2.6.0/temp/environment'. * Working |
39 |
> > directory: |
40 |
> > '/var/tmp/portage/dev-python/uranium-2.6.0/work/uranium-2.6.0_build' * S: |
41 |
> > '/var/tmp/portage/dev-python/uranium-2.6.0/work/Uranium-2.6.0' [1] 15403 |
42 |
> > exit 1 emerge media-gfx/cura |
43 |
> > |
44 |
> > But: |
45 |
> > root>python --version |
46 |
> > Python 3.5.4 |
47 |
> > |
48 |
> > eselect python list |
49 |
> > Available Python interpreters, in order of preference: |
50 |
> > [1] python3.5 |
51 |
> > [2] python3.4 |
52 |
> > [3] python2.7 |
53 |
> > |
54 |
> > |
55 |
> > How can I fix this? |
56 |
> > |
57 |
> > Thanks a lot for any help in advance! |
58 |
> > Cheers |
59 |
> > Meino |
60 |
> |
61 |
> Hi Meino, |
62 |
> |
63 |
> what do $PYTHON_SINGLE_TARGET and $PYTHON_TARGETS look like on your system |
64 |
> (check, e.g., the output of "emerge --info")? Those determine what version of |
65 |
> python the package actually uses. |
66 |
> |
67 |
> In any case, I would file a bug that apparently Python 3.4 is not supported by |
68 |
> that package anymore, so that it can be removed from the list of compatible |
69 |
> versions. |
70 |
> |
71 |
> HTH |
72 |
> -- |
73 |
> Marc Joliet |
74 |
> -- |
75 |
> "People who think they know everything really annoy those of us who know we |
76 |
> don't" - Bjarne Stroustrup |
77 |
|
78 |
Hi Marc, |
79 |
|
80 |
thanks for your reply ! :) |
81 |
|
82 |
It is not set at all. |
83 |
Is it possible to set that "locally" only fo rthe compilation |
84 |
process. I fear, that I will screw up the whole system when |
85 |
using make.conf for this purpose... |
86 |
|
87 |
Cheers |
88 |
Meino |