From: Roman Scherer <roman.scherer@burningswell.com>
To: Christopher Baines <mail@cbaines.net>
Cc: 61009@debbugs.gnu.org, leo@famulari.name
Subject: [bug#61009] [PATCH] Building Icecat and jemalloc on aarch64-linux
Date: Wed, 01 Mar 2023 19:05:38 +0100 [thread overview]
Message-ID: <87v8jkqqwd.fsf@burningswell.com> (raw)
In-Reply-To: <87v8jkwjzp.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
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 ;)
Thanks, Roman.
Christopher Baines <mail@cbaines.net> writes:
> [[PGP Signed Part:Undecided]]
>
> Roman Scherer <roman.scherer@burningswell.com> writes:
>
>> Alright, thanks Leo!
>>
>> Leo Famulari <leo@famulari.name> writes:
>>
>>> On Mon, Feb 06, 2023 at 08:52:43PM +0100, Roman Scherer wrote:
>>>> 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?
>>>
>>> No, I don't have any specific knowledge about IceCat or aarch64.
>>>
>>> Mark Weaver is the primary maintainer of our IceCat package.
>>>
>>> It seems like a mistake that IceCat would require EME on a particular
>>> architecture. Maybe the name of the configure option has changed.
>
> I've pushed one of these patches now as
> 72ec11d24f34104efce0d91050a3faba4e2c7242. I missed any other patches
> that were sent to this issue.
>
> I think removing the --disable-eme option is OK on aarch64 as it's
> probably not an option since I'm guessing EME isn't available on
> aarch64. Anyway, Icecat looks to add these disable options by default so
> I'm not sure we need it for any architecture in the guix package.
>
> [[End of PGP Signed Part]]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 528 bytes --]
next prev parent reply other threads:[~2023-03-01 18:16 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 [this message]
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=87v8jkqqwd.fsf@burningswell.com \
--to=roman.scherer@burningswell.com \
--cc=61009@debbugs.gnu.org \
--cc=leo@famulari.name \
--cc=mail@cbaines.net \
/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.