From: balejk <balejk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fractal: update to 9.
Date: Fri, 17 Jan 2025 14:10:25 +0100 [thread overview]
Message-ID: <20250117131025.44E76213E6@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54007@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
New comment by balejk on void-packages repository
https://github.com/void-linux/void-packages/pull/54007#issuecomment-2598337086
Comment:
I tried to cross build this for aarch64 as mandated by the PR template for PRs using [ci skip] and everything worked fine except my RAM wasn't large enough this time so the build got terminated. I can now also confirm that it definitely does take up more than 14 GiB at a certain moment during the build, however at the same time I was able to build it for my native arch with 16 GB RAM before.
I also tried to cross build for x86_64 (glibc) but got the following error:
```
=> ERROR: fractal-9_1: failed to install target dependencies! (error 8)
soundtouch-2.3.2_1: broken, unresolvable shlib `libmvec.so.1'
Transaction aborted due to unresolved shlibs.
```
This doesn't really sound like it's caused by this PR, or is it?
If anyone with large enough RAM was able to test this on some other archs than x86_64-musl, it would be great.
next prev parent reply other threads:[~2025-01-17 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 11:20 [PR PATCH] fractal: update to 9 balejk
2025-01-17 13:10 ` balejk [this message]
2025-04-06 6:38 ` chrysos349
2025-04-09 8:46 ` balejk
2025-04-13 18:14 ` CameronNemo
2025-05-03 17:43 ` [PR PATCH] [Updated] fractal: update to 11 balejk
2025-05-03 17:44 ` balejk
2025-05-13 19:30 ` balejk
2025-06-06 8:04 ` balejk
2025-06-08 17:10 ` Duncaen
2025-06-09 14:35 ` [PR PATCH] [Merged]: " Duncaen
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=20250117131025.44E76213E6@inbox.vuxu.org \
--to=balejk@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).