GNOME Bugzilla – Bug 765354
Autodetect the ninja-build binary
Last modified: 2018-01-28 19:29:35 UTC
Building gst-transcoder Votre branche est à jour avec 'origin/master'. La branche courante master est à jour. The Meson build system Version: 0.29.0 Source dir: gst-transcoder Build dir: gst-transcoder/build Build type: native build Build machine cpu family: x86_64 Build machine cpu: x86_64 Project name: gst-renderer Native c compiler: cc (gcc 5.3.1) Checking for function "getrusage": YES Found pkg-config: /usr/bin/pkg-config (0.28) Native dependency gobject-2.0 found: YES 2.46.2 Native dependency glib-2.0 found: YES 2.46.2 Native dependency gstreamer-1.0 found: YES 1.8.0 Native dependency gstreamer-pbutils-1.0 found: YES 1.8.0 Warning, glib compiled dependencies will not work until this upstream issue is fixed: https://bugzilla.gnome.org/show_bug.cgi?id=745754 Build targets in project: 5 cd build && ninja /bin/sh: ninja : command not found Makefile:2: recipe for target 'all' failed make: *** [all] Error 127 Could not compile gst-transcoder ; result: 0 So, the problem is that the "ninja" binary is named differently in distros like Fedora (see https://github.com/ninja-build/ninja/issues/860) and the gst-transcoder build script doesn't handle that, resulting in a thing that won't compile even if you do have ninja installed on the system. Could the presence of /usr/bin/ninja-build be detected and handled?
I think Fedora has since renamed ninja-build to ninja.
Yes.