unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Saku Laesvuori via Guix-patches via <guix-patches@gnu.org>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: 65553@debbugs.gnu.org
Subject: [bug#65553] [PATCH 0/6] gnu: Add arrayfire.
Date: Sat, 26 Aug 2023 22:18:56 +0300	[thread overview]
Message-ID: <20230826191856.lixehyli766k6oqm@X-kone> (raw)
In-Reply-To: <ce063967-c2d3-f383-e67e-057d941901e9@disroot.org>

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

> I don't know if ArrayFire builds, since on my computer all the
> RAM(4GB) is used up by the linker at some point.
>
> If anyone knows how to reduce memory usage when linking, please let me know.

I have normally solve this by just adding a huge swapfile, but if
someone knows how to actually reduce the ram usage by the linker that
would be interesting to hear.

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

  parent reply	other threads:[~2023-08-26 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26 18:46 [bug#65553] [PATCH 0/6] gnu: Add arrayfire Adam Faiz via Guix-patches via
2023-08-26 18:50 ` [bug#65553] [PATCH 1/6] gnu: Add arrayfire-glad Adam Faiz via Guix-patches via
2023-08-26 18:51 ` [bug#65553] [PATCH 2/6] gnu: Add span-lite Adam Faiz via Guix-patches via
2023-08-26 18:52 ` [bug#65553] [PATCH 3/6] gnu: Add arrayfire-threads Adam Faiz via Guix-patches via
2023-08-26 18:53 ` [bug#65553] [PATCH 4/6] gnu: Add arrayfire-forge Adam Faiz via Guix-patches via
2023-08-26 18:55 ` [bug#65553] [PATCH 5/6] gnu: Add arrayfire-docs Adam Faiz via Guix-patches via
2023-08-26 18:56 ` [bug#65553] [PATCH 6/6] gnu: Add arrayfire Adam Faiz via Guix-patches via
2023-08-26 19:18 ` Saku Laesvuori via Guix-patches via [this message]
2023-08-28  6:30   ` [bug#65553] [PATCH 0/6] " Adam Faiz via Guix-patches via

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=20230826191856.lixehyli766k6oqm@X-kone \
    --to=guix-patches@gnu.org \
    --cc=65553@debbugs.gnu.org \
    --cc=adam.faiz@disroot.org \
    --cc=saku@laesvuori.fi \
    /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).