From: Gabor Gero via <help-guix@gnu.org>
To: "Efraim Flashner" <efraim@flashner.co.il>
Cc: "help-guix" <help-guix@gnu.org>
Subject: Re: Cargo attemps to download packages already specified as cargo-inputs
Date: Tue, 24 Dec 2024 21:44:33 +0100 [thread overview]
Message-ID: <193fa6a087a.11249618a195756.3610905432969500934@zohomail.eu> (raw)
In-Reply-To: <Z2l7Nc3m-fyNvOPI@pbp>
Thanks for the help, it seems you were correct on both counts.
---- On Mon, 23 Dec 2024 16:00:35 +0100 Efraim Flashner <efraim@flashner.co.il> wrote ---
On Sun, Dec 22, 2024 at 12:06:23PM +0100, Gabor Gero via wrote:
> Hello,
>
<snip>
>
> The problem is that if I try to build it via guix build, while all the Rust dependencies get pulled in by guix perfectly fine, once it reaches the build stage, cargo prints the following warning:
> "warning: `/tmp/guix-build-pointersearcher-x-0.7.4-dylib.drv-0/source/.cargo/config` is deprecated in favor of `config.toml`
> note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`"
> and attempts to download argh and rayon. What am I doing wrong?
Oh, I responded to the warning and not the actual problem.
I see that command/Cargo.toml gives a git url for argh, that might need
to be patched to refer to a released version which you'd provide. Also
in libptrscan/Cargo.toml it lists a dependency on machx-0.4 which you
might also need to add.
--
Efraim Flashner <mailto:efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
prev parent reply other threads:[~2024-12-24 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 11:06 Cargo attemps to download packages already specified as cargo-inputs Gabor Gero via
2024-12-23 14:55 ` Efraim Flashner
2024-12-23 15:01 ` Efraim Flashner
2024-12-24 20:44 ` Gabor Gero via [this message]
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=193fa6a087a.11249618a195756.3610905432969500934@zohomail.eu \
--to=help-guix@gnu.org \
--cc=efraim@flashner.co.il \
--cc=gaga.gero@zohomail.eu \
/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.