Re: Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Miro HronĨok
On 24. 02. 19 16:05, Charalampos Stratakis wrote: This is an issue with the build dependencies. python3 should be replaced with python3-devel. From the SPEC on the build section: %cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=%{__python3} .. The %{__python3} macro will be defined when

Re: Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Artur Iwicki
The builds for the previous versions succeeded with a python3 BR, so either something has changed along the way, or the package has a bit of a history with accidentally successful builds. :) Either way - changing the BR to python3-devel worked! Thanks for the help. __

Re: Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Artur Iwicki
Done; committed and pushed. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproje

Re: Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Charalampos Stratakis
- Original Message - > From: "Artur Iwicki" > To: devel@lists.fedoraproject.org > Sent: Sunday, February 24, 2019 3:27:43 PM > Subject: Problem with cmake's PythonInterp in F29 and F28 > > I've got a package (colobot) which has a build-time depe

Re: Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Artur Iwicki
Yeah, I made the mistake of putting some music in the repo instead of the cache. I wanted to write "too late to fix that now", but now that I think of it - well, doing a full `git clone` will still be slow, but at least `--depth=1` clones will go fast. I'll make a commit that moves the files to

Re: Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Rex Dieter
Artur Iwicki wrote: > I've got a package (colobot) which has a build-time dependency on Python3. > The program had a new upstream release today, so I updated the spec file > and fired up the builds. > > Everything went smooth on rawhide and F30, whereas the F29 and F28 builds > failed with a rath

Problem with cmake's PythonInterp in F29 and F28

2019-02-24 Thread Artur Iwicki
I've got a package (colobot) which has a build-time dependency on Python3. The program had a new upstream release today, so I updated the spec file and fired up the builds. Everything went smooth on rawhide and F30, whereas the F29 and F28 builds failed with a rather amusing error message: >BUI