From: Andrey Grozin <grozin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] problems with media-gfx/asymptote
Date: Tue, 18 Feb 2025 12:18:53 +0000 (UTC) [thread overview]
Message-ID: <037e2c8f-2e80-1879-21fd-0d3871897ed4@gentoo.org> (raw)
Hello *,
asymptote-3.00 has just appeared, and I'm trying to update the ebuild.
asymptote now bundles boehm-gc; the option to use system boehm-gc is now
absent. asymptote-3.00/gc/README.md says that it's 8.2.8; however, the
sourse tree asymptote-3.00/gc differs from the plain gc-8.2.8. I suppose
some hacking autoconf files is needed to unbundle it, and it's a
nontrivial work. A pity.
What's more, compiling this bundled gc leads to sandbox violations like
F: open_wr
S: deny
P: /proc/4643/clear_refs
A: /proc/4643/clear_refs
R: /proc/4643/clear_refs
C: ./cordtest
and several more. All of them are in some test programs:
cordtest
gctest
staticrootstest
disclaim_test
disclaim_weakmap_test
All of them try to write to some /proc/*/clear_refs; I don't know what are
these /proc/*/clear_refs files. Surprisingly, all gc test are marked as
passed. Maybe, the resulting libgc (and the resulting asymptote) even
work. But, of course, the ebuild fails, and does not install these results.
Interestingly, emerging boehm-gc succeeds, no sandbox violations.
I suppose the best way out is to somehow force asymptote to use the system
boehm-gc. As a stopgap measure, is it possible to allow these test
programs to write to /proc/*/clear_refs?
Hoping for some help,
Andrey
next reply other threads:[~2025-02-18 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 12:18 Andrey Grozin [this message]
2025-02-18 14:37 ` [gentoo-dev] problems with media-gfx/asymptote Jérôme Carretero
2025-02-18 19:03 ` Andrey Grozin
2025-02-19 4:40 ` [gentoo-dev] sandbox and /proc/<pid>/clear_refs [was: problems with media-gfx/asymptote] Andrey Grozin
2025-02-19 5:02 ` Mike Gilbert
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=037e2c8f-2e80-1879-21fd-0d3871897ed4@gentoo.org \
--to=grozin@gentoo.org \
--cc=gentoo-dev@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