From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gjs: update to 1.78.3.
Date: Tue, 06 Feb 2024 14:18:48 +0100 [thread overview]
Message-ID: <20240206131848.C12D92477B@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48560@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/48560#issuecomment-1929558523
Comment:
Looked in to the gjs build failure on armv7l-glibc a bit. It also happens with mozjs102, but it doesn't happen when 'native' compiling armv7l with binfmt. I tried using qemu-user-static-7.1.0, which I know worked with cross compiling gjs and the same error occurred.
I assume this is related to the armv7l cross compilers, I'll look in to this more later.
next prev parent reply other threads:[~2024-02-06 13:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 10:18 [PR PATCH] " oreo639
2024-02-06 13:17 ` oreo639
2024-02-06 13:17 ` oreo639
2024-02-06 13:18 ` oreo639
2024-02-06 13:18 ` oreo639 [this message]
2024-02-06 13:39 ` oreo639
2024-02-06 13:52 ` oreo639
2024-02-06 14:16 ` chrysos349
2024-02-06 14:18 ` chrysos349
2024-02-06 15:39 ` oreo639
2024-02-06 15:40 ` oreo639
2024-02-06 15:41 ` oreo639
2024-02-06 15:41 ` oreo639
2024-02-06 15:43 ` oreo639
2024-02-06 15:54 ` oreo639
2024-02-06 15:54 ` oreo639
2024-02-06 15:55 ` oreo639
2024-02-06 15:56 ` oreo639
2024-02-06 16:35 ` chrysos349
2024-02-06 16:41 ` oreo639
2024-02-06 18:29 ` oreo639
2024-02-06 18:30 ` oreo639
2024-02-06 21:12 ` oreo639
2024-02-06 21:25 ` [PR PATCH] [Updated] " oreo639
2024-02-07 21:32 ` oreo639
2024-02-16 14:21 ` chrysos349
2024-02-17 8:13 ` [PR PATCH] [Updated] " oreo639
2024-02-17 8:13 ` oreo639
2024-02-19 21:05 ` chrysos349
2024-02-20 14:56 ` sgn
2024-02-26 5:31 ` [PR PATCH] [Updated] " oreo639
2024-02-29 20:51 ` oreo639
2024-03-05 0:17 ` [PR PATCH] [Merged]: " oreo639
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=20240206131848.C12D92477B@inbox.vuxu.org \
--to=oreo639@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).