From: Andreas Enge <andreas@enge.fr>
To: Eric Le Bihan <eric.le.bihan.dev@free.fr>
Cc: guix-devel@gnu.org
Subject: Re: rust work in progress conflicts
Date: Fri, 29 Jul 2016 11:03:41 +0200 [thread overview]
Message-ID: <20160729090341.GA2308@solar> (raw)
In-Reply-To: <20160728203144.7df4bb8c@itchy>
Hello,
On Thu, Jul 28, 2016 at 08:31:44PM +0200, Eric Le Bihan wrote:
> 1. I can compile a sample program in a guix environment created using
> `guix environment gcc glibc binutils rust`, but the program
> generated fails to run because libgcc_s.so.1 can not be found. How can
> it be added to the environment?
I would suggest to replace "gcc glibc binutils" by "gcc-toolchain", which
installs a specially modified linker.
Andreas
next prev parent reply other threads:[~2016-07-29 9:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 17:45 LLVM: "FileCheck" is missing Danny Milosavljevic
2016-03-25 21:58 ` Nils Gillmann
2016-03-25 22:06 ` rust work in progress conflicts (was: Re: LLVM: "FileCheck" is missing) Nils Gillmann
2016-05-04 10:34 ` Jelle Licht
2016-05-05 13:35 ` rust work in progress conflicts Ludovic Courtès
2016-05-05 14:46 ` Alex Griffin
2016-05-06 9:05 ` Andy Wingo
2016-05-06 9:15 ` Andy Wingo
2016-05-06 9:59 ` Ludovic Courtès
2016-05-05 15:06 ` ng0
2016-07-28 8:28 ` ng0
2016-07-28 18:31 ` Eric Le Bihan
2016-07-29 9:03 ` Andreas Enge [this message]
2016-07-29 11:40 ` Vincent Legoll
2016-07-29 14:37 ` ng0
2016-07-30 10:04 ` Eric Le Bihan
2016-07-29 15:16 ` Rust Ludovic Courtès
2016-07-29 15:34 ` Rust Alex Griffin
2016-07-29 16:08 ` Rust Jelle Licht
2016-07-30 13:34 ` Rust Ludovic Courtès
2016-07-30 17:57 ` Rust Pjotr Prins
2016-07-30 11:01 ` Rust Eric Le Bihan
2016-07-30 13:44 ` Rust Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2016-07-29 9:46 rust work in progress conflicts David Craven
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=20160729090341.GA2308@solar \
--to=andreas@enge.fr \
--cc=eric.le.bihan.dev@free.fr \
--cc=guix-devel@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).