all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roman Scherer <roman.scherer@burningswell.com>
To: Leo Famulari <leo@famulari.name>
Cc: 61009@debbugs.gnu.org
Subject: [bug#61009] [PATCH] Building Icecat and jemalloc on aarch64-linux
Date: Mon, 06 Feb 2023 20:52:43 +0100	[thread overview]
Message-ID: <86zg9q1ryl.fsf@burningswell.com> (raw)
In-Reply-To: <Y9/oOdnBZpzPxml5@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]


Hi Leo,

thanks for your reply. Ok, I understand. I try to see if I can disable
it in some other way then. Are you familiar with this? Do you have any
tips to share?

I think the v2 patches about transparent huge pages for jemalloc could
still be an improvement, if it's a compatible change. It would enable
the use of rust substitutes that depend on jemalloc on aarch64 that run
with kernel pages > 4K.

Roman

Leo Famulari <leo@famulari.name> writes:

> On Sun, Jan 22, 2023 at 09:06:43PM +0100, Roman Scherer wrote:
>> 2. Disable EME on aarch64-linux
>>
>> I removed the --disable-eme option on aarch64-linux because the configure
>> script failed an error saying this option is not supported on this
>> architecture. Since EME stands for Encrypted Media Extensions and is a
>> JavaScript API for playing DRMed video content in HTML, I'm not sure if this
>> is ok, or what to best do here?
>
> Guix adheres to the Free System Distribution Guidelines, which
> explicitly forbids browsers with EME support:
>
> https://guix.gnu.org/en/about/
> https://www.gnu.org/distros/free-system-distribution-guidelines.en.html
>
> Unfortunately, I don't know the answers to your other questions.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]

  reply	other threads:[~2023-02-06 20:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 20:06 [bug#61009] [PATCH] Building Icecat and jemalloc on aarch64-linux Roman Scherer
2023-02-05 16:35 ` [bug#61009] [PATCH v2] " Roman Scherer
2023-02-05 17:32 ` [bug#61009] [PATCH] " Leo Famulari
2023-02-06 19:52   ` Roman Scherer [this message]
2023-02-09 12:49     ` Leo Famulari
2023-02-11  9:44       ` Roman Scherer
2023-03-01 15:46         ` Christopher Baines
2023-03-01 18:05           ` Roman Scherer
2023-03-02 10:07             ` Christopher Baines

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=86zg9q1ryl.fsf@burningswell.com \
    --to=roman.scherer@burningswell.com \
    --cc=61009@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.