From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15176] udisks-2.9.4 build fails with per-package
Date: Fri, 16 Dec 2022 12:42:21 +0000 [thread overview]
Message-ID: <bug-15176-163-uOikrAxCbl@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15176-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15176
--- Comment #1 from Michael Nosthoff <buildroot@heine.tech> ---
I just realized the same is happening with gvfs for which some extra handlings
is alread in the polkit.mk file.
[88/263] Generating daemon/org.gtk.vfs.file-operations.policy with a custom
command
FAILED: daemon/org.gtk.vfs.file-operations.policy
/build/buildroot/build/per-package/gvfs/host/bin/meson --internal msgfmthelper
--msgfmt=/build/buildroot/build/per-package/gvfs/host/bin/msgfmt
daemon/org.gtk.vfs.file-operations.policy.in
daemon/org.gtk.vfs.file-operations.policy xml
/build/buildroot/build/build/gvfs-1.48.1/po
/build/buildroot/build/per-package/gvfs/host/bin/msgfmt: cannot locate ITS
rules for daemon/org.gtk.vfs.file-operations.policy.in
[113/263] Compiling C object
common/libgvfscommon.so.p/meson-generated_.._gvfsdbus.c.o
ninja: build stopped: subcommand failed.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-16 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 8:19 [Buildroot] [Bug 15176] New: udisks-2.9.4 build fails with per-package bugzilla
2022-12-16 12:42 ` bugzilla [this message]
2023-01-28 21:28 ` [Buildroot] [Bug 15176] " bugzilla
2024-06-15 15:04 ` bugzilla
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=bug-15176-163-uOikrAxCbl@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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