From: Apoorv via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Ekaitz Zarraga <ekaitz@elenq.tech>
Subject: Re: Suggestion for a guix shell feature.
Date: Fri, 5 Jan 2024 14:38:35 +0100 (CET) [thread overview]
Message-ID: <NnOqCFn--3-9@tuta.io> (raw)
In-Reply-To: <87plyi5mh3.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
Tried to use to antioxydant build system, I cannot seem to add it as a channel but was able to clone the repo and authenticate it manually.. then guix build -L . -f antioxidant-packages.scm fails to run with error,
ice-9/eval.scm:223:20: In procedure proc:
error: rust-sequoia-ipc-0.26: unbound variable
hint: Did you forget a `use-modules' form?
I think I am going to stick to adding libs to LD_LIBRARY_PATH manually as it works even though I know you said its wrong.
--
Sent with Tuta; enjoy secure & ad-free emails:
https://tuta.com
Jan 3, 2024, 17:57 by maxim.cournoyer@gmail.com:
> Hi,
>
> Apoorv <apoorvs@tuta.io> writes:
>
>> OK, it was my bad I had an older copy of guix.scm file I was passing
>> that, it didn't have cargo-build-system. But now I'm getting so many
>> other errors related to cargo deps missing or version mismatch, I
>> tried adding those deps spent like 1-2 hours but something dep was
>> still missing or version mismatch, finally I gave up. I'm not sure how
>> many deps I have to add like this.. this is getting way to complicated
>> then it needs to be.
>>
>
> cargo/rust is poorly integrated in Guix, as there's some impedance
> mismatch between package handling by Guix and Cargo itself, which would
> rather take care of it.
>
> I'd expect most Rust developpers using Guix only do so to provide
> Rust/Cargo, and let Cargo take care of the rest. Otherwise you'd need
> to replicate the pain the cargo-build-system goes through to make it
> work.
>
> A more future-proof approach if you'd like to improve Rust integration
> into Guix would be to continue integrating the 'antioxydant' build
> system effort started by Maxime Devos [0], which doesn't rely on Cargo
> to build Rust crates (and supports dynamic linking of Rust libraries, I
> think?).
>
> [0] https://notabug.org/maximed/cargoless-rust-experiments
>
> --
> Thanks,
> Maxim
>
[-- Attachment #2: Type: text/html, Size: 3152 bytes --]
next prev parent reply other threads:[~2024-01-05 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <NmrVHaU--3-9@tuta.io>
2023-12-30 3:10 ` Suggestion for a guix shell feature Maxim Cournoyer
2023-12-31 12:10 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-31 16:55 ` Maxim Cournoyer
2024-01-01 3:01 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-02 16:33 ` Maxim Cournoyer
2024-01-03 9:14 ` Apoorv via Development of GNU Guix and the GNU System distribution.
2024-01-03 17:57 ` Maxim Cournoyer
2024-01-05 13:38 ` Apoorv via Development of GNU Guix and the GNU System distribution. [this message]
2023-12-21 16:10 Apoorv via Development of GNU Guix and the GNU System distribution.
2023-12-29 3:58 ` Maxim Cournoyer
2023-12-29 13:50 ` Ekaitz Zarraga
2023-12-29 15:39 ` Tobias Geerinckx-Rice
2023-12-29 17:21 ` Maxim Cournoyer
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=NnOqCFn--3-9@tuta.io \
--to=guix-devel@gnu.org \
--cc=apoorvs@tuta.io \
--cc=ekaitz@elenq.tech \
--cc=maxim.cournoyer@gmail.com \
--cc=me@tobias.gr \
/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).