From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2022-01-12
Date: Thu, 13 Jan 2022 10:53:18 +0200 [thread overview]
Message-ID: <20220113105318.GC97860@momiji> (raw)
In-Reply-To: <20220113071133.371F0415E6@smtp4.osuosl.org>
[-- Attachment #1.1: Type: text/plain, Size: 1722 bytes --]
On Thu, 13 Jan 2022 07:06:44 +0000 Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Detail of failures for master
> -----------------------------
>
> arch | reason | OK? | url | orph?
> -------------+--------------------------------+-----+---------------------------------------------------------------------------------+-------
>
> [...]
>
> arm | gcr-3.40.0 | NOK | http://autobuild.buildroot.net/results/cdd5c721544d6f07c51be536e414fa474f4b907b | ORPH
> riscv64 | gcr-3.40.0 | NOK | http://autobuild.buildroot.net/results/8cecd33d7772b19d60f70a097dcb1623bb3ee7de | ORPH
I ran into the same issue while trying out the switch to Ninja for CMake
packages, because trying to build "midori" pulls in "gcr" as a dependency.
These build failures in "gcr" have been caused by the update to Meson 0.61;
there is an upstream fix here:
https://gitlab.gnome.org/GNOME/gcr/-/merge_requests/81.patch
Applying this patch locally made the configure step complete, but then the
build step ran into this other issue:
[1/114] Generating gck/gck-1.vapi with a custom command
FAILED: gck/gck-1.vapi
[...]
Unknown option --metadatdir=/home/aperez/buildroot/output-cmake/build/gcr-3.40.0/gck
Run '/home/aperez/buildroot/output-cmake/per-package/gcr/host/bin/vapigen-0.52 --help' to see a full list of available command line options.
ninja: build stopped: subcommand failed.
I am trying to fix this other issue before submitting a patch for the "gcr"
package. If this second failure rings a bell to anyone, I am all ears^W eyes.
Cheers,
—Adrián
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-13 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 7:06 [Buildroot] [autobuild.buildroot.net] Daily results for 2022-01-12 Thomas Petazzoni
2022-01-13 8:53 ` Adrian Perez de Castro [this message]
2022-01-13 9:12 ` Adrian Perez de Castro
2022-01-13 12:02 ` Adrian Perez de Castro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220113105318.GC97860@momiji \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox