From: "Jonas Møller via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>,
"65461@debbugs.gnu.org" <65461@debbugs.gnu.org>
Subject: bug#65461: Cannot compile any Rust projects
Date: Fri, 25 Aug 2023 13:30:00 +0000 [thread overview]
Message-ID: <Dx9aLxyxnyq7hnClNq57aNab67Fzmxwm_NxXnJP5tCC_YyyG0cTXle6QUNojPxAYG8f-UszcgBrF-1YmJ7V24PQngCCHVPJ5MV9eFhQwVqY=@moesys.no> (raw)
In-Reply-To: <87wmxjth0t.fsf@jpoiret.xyz>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
I can still reproduce this with:
guix shell —container rust rust-cargo
cargo new hello
cd hello
cargo build
Mvh Jonas Møller
On Fri, Aug 25, 2023 at 15:58, Josselin Poiret <[dev@jpoiret.xyz](mailto:On Fri, Aug 25, 2023 at 15:58, Josselin Poiret <<a href=)> wrote:
> Hi Jonas,
>
> Jonas via Bug reports for GNU Guix <bug-guix@gnu.org> writes:
>
>> Hi! Compiling any Rust projects with cargo/rustc gives me:
>>
>> error: linking with
>> `/gnu/store/5lqhcv91ijy82p92ac6g5xw48l0lwwz4-gcc-11.3.0/bin/gcc` failed:
>> exit status: 1
>
> Please make sure you add simple reproducers to your bug reports so that
> people can check that the bug does get resolved by proposed patches. I
> can't reproduce this with a simple `rustc hello.rs` where `hello.rs` is
> the simplest hello world I could find.
>
> Best,
> --
> Josselin Poiret
[-- Attachment #2: Type: text/html, Size: 3696 bytes --]
next prev parent reply other threads:[~2023-08-25 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 22:59 bug#65461: Cannot compile any Rust projects Jonas via Bug reports for GNU Guix
2023-08-23 3:36 ` Hilton Chain via Bug reports for GNU Guix
2023-08-23 18:22 ` brian via Bug reports for GNU Guix
2023-08-24 2:08 ` Hilton Chain via Bug reports for GNU Guix
2023-08-25 11:03 ` Josselin Poiret via Bug reports for GNU Guix
2023-08-25 16:37 ` Josselin Poiret via Bug reports for GNU Guix
2023-08-25 12:58 ` Josselin Poiret via Bug reports for GNU Guix
2023-08-25 13:30 ` Jonas Møller via Bug reports for GNU Guix [this message]
2023-08-29 21:03 ` 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='Dx9aLxyxnyq7hnClNq57aNab67Fzmxwm_NxXnJP5tCC_YyyG0cTXle6QUNojPxAYG8f-UszcgBrF-1YmJ7V24PQngCCHVPJ5MV9eFhQwVqY=@moesys.no' \
--to=bug-guix@gnu.org \
--cc=65461@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=jonas@moesys.no \
/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).