On 03. 06. 23 13:29, Mattia Verga wrote:
In the test section of libindi package I use this to run tests:
%ctest --test-dir %_vpath_builddir/test
This translates in Fedora as:
+ /usr/bin/ctest --test-dir redhat-linux-build --output-on-failure
--force-new-ctest-process -j6 --test-dir redhat-linux-build/test
Internal ctest changing into directory:
/builddir/build/BUILD/indi-2.0.2/redhat-linux-build/test
While on EPEL (at least, in COPR):
+ /usr/bin/ctest --output-on-failure --force-new-ctest-process -j2 --test-dir
redhat-linux-build/test
Internal ctest changing into directory:
/builddir/build/BUILD/indi-2.0.2/redhat-linux-build/redhat-linux-build/test
Failed to change working directory to
"/builddir/build/BUILD/indi-2.0.2/redhat-linux-build/redhat-linux-build/test" :
No such file or directory
I'm not sure against what package I should report this. Python-rpm-macros seems a
Fedora package only, I don't see any epel9 build there.
It's not in epel because it is in RHEL.
And, most important, I don't know if I'm doing something
wrong or if is indeed something to report.
Can anyone clarify me these two things?
I have no idea. What makes you suspect this problem is related to *Python*
macros at all? %ctest is defined in /usr/lib/rpm/macros.d/macros.cmake which is
shipped by cmake-rpm-macros, a subpackage of cmake.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok