From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Tracking: packages broken on larger pagesize kernels (like rpi5-kernel)
Date: Wed, 17 Jan 2024 20:34:17 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48260@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
New issue by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48260
Description:
Some programs have issues when running on kernels with larger pagesizes.
### jemalloc
One common case is programs (especially rust programs) that use jemalloc. this was fixed in #48194 for the jemalloc package itself and all rust packages built in the future. This often manifests itself like this:
```
<jemalloc>: Unsupported system page size
<jemalloc>: Unsupported system page size
memory allocation of 5 bytes failed
```
### Probably bad
*as yet untested, based on https://github.com/AsahiLinux/docs/wiki/Broken-Software#broken-packages*
- [ ] qt5-webengine
- [ ] qt6-webengine (qt6-pdf?)
- [ ] zig
next reply other threads:[~2024-01-17 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 19:34 classabbyamp [this message]
2024-01-17 21:20 ` dkwo
2024-05-13 20:08 ` dkwo
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48260@inbox.vuxu.org \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).