From: "Anna “CyberTailor”" <cyber@sysrq.in>
To: gentoo-guru@lists.gentoo.org
Subject: Re: [gentoo-guru] Sandbox violations with meson / ninja in ebuild
Date: Sun, 10 Apr 2022 10:41:59 +0500 [thread overview]
Message-ID: <YlJuJ+WmHEiTsoXY@sysrq.in> (raw)
In-Reply-To: <20220410052827.qoo46fpibgtyfz7s@localhost>
On 2022-04-10 08:28, Dex Conner wrote:
> Hello everyone,
>
> I'm trying to write an ebuild for somebar and it uses meson and ninja to
> configure / build. I've set
>
> meson -Dprefix="${D}" build
This is wrong. ${D} is only defined in src_install. Don't override
standard phase function and see whether it works.
> and I'm getting
>
> >>> Install gui-apps/somebar-9999 into /var/tmp/portage/gui-apps/somebar-9999/image
>
> as expected but I'm also still getting
>
> * ACCESS DENIED: SYMLINK: /usr/lib64/libcrypt.so.2
> * ACCESS DENIED: SYMLINK: /usr/lib/libcrypt.so.2
> * ACCESS DENIED: open_wr: /etc/ld.so.cache~
>
> F: SYMLINK
> S: deny
> P: /usr/lib64/libcrypt.so.2
> A: /usr/lib64/libcrypt.so.2
> R: /usr/lib64/libcrypt.so.2
> C: ldconfig -v
>
> F: SYMLINK
> S: deny
> P: /usr/lib/libcrypt.so.2
> A: /usr/lib/libcrypt.so.2
> R: /usr/lib/libcrypt.so.2
> C: ldconfig -v
>
> F: open_wr
> S: deny
> P: /etc/ld.so.cache~
> A: /etc/ld.so.cache~
> R: /etc/ld.so.cache~
> C: ldconfig -v
>
> Do you have any ideas as to how to work with this? Can you point me to
> some other ebuilds using meson / ninja?
See example in:
$ man meson.eclass
> Thank you!
>
> --
> Dex
next prev parent reply other threads:[~2024-11-24 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 5:28 [gentoo-guru] Sandbox violations with meson / ninja in ebuild Dex Conner
2022-04-10 5:41 ` Anna “CyberTailor” [this message]
2022-04-10 6:26 ` Dex Conner
2022-04-10 6:36 ` Dex Conner
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=YlJuJ+WmHEiTsoXY@sysrq.in \
--to=cyber@sysrq.in \
--cc=gentoo-guru@lists.gentoo.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