unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Albin Otterhäll" <albin@a12l.xyz>
To: 61284@debbugs.gnu.org
Subject: bug#61284: [rust] Segfault when trying to download dependencies using Cargo
Date: Sun, 05 Feb 2023 00:28:25 +0000	[thread overview]
Message-ID: <ePDsFA2AuFFcz98E3ozd2k_yU3S6TD2tnDmYfY6F9XmKlmptcLi7NRCka_sMMPoqsF4_7xSI2-mkExyBLxrhyM2cpOLB3z4Lq9iaUnS8sDc=@a12l.xyz> (raw)

# Segfault when trying to build Rust binary using cargo and a dependency

## Description

As soon as I add a dependency to `Cargo.toml` I get a segfault when I in some way try to build the binary.

## Expected behavior

When running `cargo build` after having added a dependency on `rand = "0.8.3"` in the example below Cargo should download the `rand` package (`rust-rand` in Guix).

## Actual behavior

The build process halts with a segmentation fault.

### Steps to reproduce

Create an environment with the command `guix shell --manifest=manifest.scm` and there `manifest.scm` contains

```
(specifications->manifest (list "rust"
                                "rust-analyzer"
                                "rust-cargo"))
```

and then run the commands

$ cargo new mve
Created binary (application) `mve` package

$ cd mve/

mve $ cargo build
   Compiling mve v0.1.0 (/home/a12l/Long-Term/TRPL/mve)
    Finished dev [unoptimized + debuginfo] target(s) in 0.56s

mve $ echo 'rand = "0.8.3"' >> Cargo.toml

mve $ cargo build
    Updating crates.io index
Segmentation fault (core dumped)

## My system

I'm running Guix on a NixOS 22.11 machine, by having added `https://github.com/foo-dogsquared/nix-overlay-guix` to my system configuration.

Thanks!
--
Albin Otterhäll




                 reply	other threads:[~2023-02-05  0:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='ePDsFA2AuFFcz98E3ozd2k_yU3S6TD2tnDmYfY6F9XmKlmptcLi7NRCka_sMMPoqsF4_7xSI2-mkExyBLxrhyM2cpOLB3z4Lq9iaUnS8sDc=@a12l.xyz' \
    --to=albin@a12l.xyz \
    --cc=61284@debbugs.gnu.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.
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).