GNOME Bugzilla – Bug 785491
Gnome-Builder build fails from error in building gst-plugins-bad
Last modified: 2017-08-16 07:29:43 UTC
Hi, I am trying to build gnome-builder from source. i did jhbuild build gnome-builder. The build failed as gst-plugins-bad could not be built. Complete log is here : https://paste.gnome.org/pewnqrh2q my operating system is fedora 26. Webkit, Devhelp modules could not be built as they too need gst-plugins-bad any other information - please ask me - karan26.ahuja@gmail.com
Any chance you could try with Meson from git? I think this issue may have been fixed by this pull request: https://github.com/mesonbuild/meson/pull/2095
Yes. i shall try to do this and reply. Best Regards, Karan
This should be fixed in upstream meson indeed. You can "make it work" of course by installing the -devel package, but then you can't trust the build (well you can't trust any GIR generated by meson prior to that change really, it could be against older library, -bad is worst as it's an unstable API).
Hi I did a git clone to get latest meson. git clone https://github.com/mesonbuild/meson.git after cloning - i renamed it to meson-0.41.2 i deleted existing meson folder from my computer at ~/jhbuild/checkout/ i pasted the latest meson cloned from git and it now looks as -> ~/jhbuild/checkout/meson-0.41.2 so the latest meson code is now inside jhbuild/checkout/meson-0.41.2 i then did jhbuild build gnome-builder I got same error as saved below https://paste.gnome.org/ppf2tods1 Please let me know if i am missing something. Thank you for your support. Best Regards, Karan
It still appears to be using the last release instead of git. It should say this in the output > Version: 0.42.0.dev1 but it says (line 22-23): > The Meson build system > Version: 0.41.2
can you please tell me how i can ask jhbuild to use the latest version ?
*** Bug 785526 has been marked as a duplicate of this bug. ***
Tim-Philipp, Thanks for CCing me. karan ahuja, The proper way to ask them is to file a bug report to JHBuild product in this very same bugzilla. However, I assume they will prefer to wait for a new meson release, as jhbuild currently is set to use tarballs from meson, and doesn't seem to exist a tarball for 0.42.0.dev1. I've done some local tests in my JHBuild and reached satisfactory results with latest meson commit. Case you want to try it too, here's what I did: 1- Set "use_local_modulesets" to "true" in my jhbuildrc (config file) in order to use local moduleset files; 2- Edited <jhbuilddir>/modulesets/gnome-suites-core-deps-3.26.modules (the default moduleset) to change meson build system from "github-tar (tarball) to "github.com" (git-clone). Here is a diff: --- a/modulesets/gnome-suites-core-deps-3.26.modules +++ b/modulesets/gnome-suites-core-deps-3.26.modules @@ -1523,11 +1523,7 @@ </cmake> <distutils id="meson" python3="1"> - <branch repo="github-tar" - version="0.41.2" - module="mesonbuild/meson/releases/download/${version}/meson-${version}.tar.gz" - checkoutdir="meson-${version}" - hash="sha256:074dd24fd068be0893e2e45bcc35c919d8e12777e9d6a7efdf72d4dc300867ca"/> + <branch repo="github.com" checkoutdir="meson" module="mesonbuild/meson.git"/> <dependencies> <dep package="ninja"/> </dependencies> 3- Finally, ran jhbuild build gst-plugins-bad (also had to re-ran Configure step).
Meson updated to 0.42.0 in JHBuild (https://git.gnome.org/browse/jhbuild/commit/?id=9514f45bf7eaefa97414666796bd9b895c88b578) I'm unable to test now, but this bug is probably resolved now.
Thanks! Let's close this then.