From: Andrey Grozin <grozin@woodpecker.gentoo.org>
To: Paul Zander <paul.zander@uni-rostock.de>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] fricas[doc] now fails to emerge
Date: Sun, 18 Aug 2024 16:20:05 +0000 (UTC) [thread overview]
Message-ID: <bb4927ba-5ced-3352-86bb-d87f37ceaab6@woodpecker.gentoo.org> (raw)
In-Reply-To: <e383fc49-484a-493a-bb2b-e1e684bb87fd@uni-rostock.de>
On Sat, 17 Aug 2024, Paul Zander wrote:
> Check the logfile at ${T}/Xvfb.log
It says
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
and then zillion times
libEGL warning: failed to open /dev/dri/card0: Permission denied
Recently I've upgraded mesa to 24.2.0. Can this problem be related to this
upgrade?
The day before yesterday, I've bumped clozurecl to 1.13. Naturally, I
decided to check that it can compile maxima and fricas, and that they
work. fricas emerged fine, with USE=doc. Then I started to emerge -auvND
@world, in particular, it was going to rebuild maxima and fricas again,
with sbcl (I normally use sbcl, not clozurecl). And energing fricas has
failed. The same day, maybe, an hour later. In between a number of
packaged were upgraded. The most suspicious one is mesa - it may be
somehow related to the behavior of Xvfb.
Can anybody with the current mesa try to emerge fricas[doc] and tell us if
it works (any lisp will do, probably, sbcl is the most reasonable one; by
the way, clozurecl compiles fricas very quickly).
Andrey
next prev parent reply other threads:[~2024-08-18 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 14:46 [gentoo-dev] fricas[doc] now fails to emerge Andrey Grozin
2024-08-17 17:13 ` Robin H. Johnson
2024-08-17 18:04 ` negril.nx+gentoo
[not found] ` <e383fc49-484a-493a-bb2b-e1e684bb87fd@uni-rostock.de>
2024-08-18 16:20 ` Andrey Grozin [this message]
2024-08-19 18:18 ` Robin H. Johnson
2024-08-19 19:49 ` Ulrich Mueller
2024-08-20 14:52 ` Robin H. Johnson
2024-08-20 16:06 ` Paul Zander
2024-08-20 19:18 ` Robin H. Johnson
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=bb4927ba-5ced-3352-86bb-d87f37ceaab6@woodpecker.gentoo.org \
--to=grozin@woodpecker.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=paul.zander@uni-rostock.de \
/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