From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15176] New: udisks-2.9.4 build fails with per-package
Date: Fri, 16 Dec 2022 08:19:20 +0000 [thread overview]
Message-ID: <bug-15176-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15176
Bug ID: 15176
Summary: udisks-2.9.4 build fails with per-package
Product: buildroot
Version: 2022.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: buildroot@heine.tech
CC: buildroot@uclibc.org
Target Milestone: ---
When using per-package build the build of udisks fails with the following error
msg:
cp org.freedesktop.UDisks2.conf.in org.freedesktop.UDisks2.conf
GEN org.freedesktop.UDisks2.policy
/build/buildroot/build/per-package/udisks/host/bin/msgfmt: cannot locate ITS
rules for org.freedesktop.UDisks2.policy.in
make[5]: *** [Makefile:924: org.freedesktop.UDisks2.policy] Error 1
make[4]: *** [Makefile:632: all-recursive] Error 1
make[3]: *** [Makefile:514: all-recursive] Error 1
make[2]: *** [Makefile:446: all] Error 2
make[1]: *** [package/pkg-generic.mk:293:
/build/buildroot/build/build/udisks-2.9.4/.stamp_built] Error 2
make: *** [Makefile:23: _all] Error 2
I tried to figure out what dependency might be missing but wasn't successful.
Any hints welcome!
--
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 reply other threads:[~2022-12-16 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 8:19 bugzilla [this message]
2022-12-16 12:42 ` [Buildroot] [Bug 15176] udisks-2.9.4 build fails with per-package bugzilla
2023-01-28 21:28 ` 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@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