unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Roman Scherer <roman.scherer@burningswell.com>
Cc: 61009-done@debbugs.gnu.org, 61009@debbugs.gnu.org
Subject: [bug#61009] [PATCH] Building Icecat and jemalloc on aarch64-linux
Date: Thu, 02 Mar 2023 10:07:17 +0000	[thread overview]
Message-ID: <877cvzv4fe.fsf@cbaines.net> (raw)
In-Reply-To: <87v8jkqqwd.fsf@burningswell.com>

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


Roman Scherer <roman.scherer@burningswell.com> writes:

> Hi Christopher,
>
> thanks for applying the patch and for the explanation.
>
> Not sure what you meant by "missed". But, I sent an improved version of
> the jemalloc patches as a separate issue a while ago. They are here:
>
> https://lists.gnu.org/archive/html/guix-patches/2023-02/msg00698.html
>
> Without the jemalloc patches, Icecat and all other packages using
> jemalloc crash with the error `<jemalloc>: Unsupported system page size`
> on aarch64 systems that run with kernel page sizes > 4K.
>
> If you are familiar with this, I could need some help here as well ;)

Sending the jemalloc patch seperately sounds good. I'm going to mark
this issue as done since that's tracked separately.

I've replied to that separate issue, but I think that these changes may
already be in place on core-updates. I'm going to have a go at merging
master in to core-updates which should allow for testing icecat in
core-updates with the changes I've merged in master.

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

      reply	other threads:[~2023-03-02 10:23 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
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 [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877cvzv4fe.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=61009-done@debbugs.gnu.org \
    --cc=61009@debbugs.gnu.org \
    --cc=roman.scherer@burningswell.com \
    /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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).