Re: rust work in progress conflicts

Le Fri, 29 Jul 2016 11:03:41 +0200, Andreas Enge a écrit : > 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

Re: rust work in progress conflicts

Vincent Legoll writes: >> 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

Re: rust work in progress conflicts

Hi Eric! Nice! 1. Try using 'guix environment --ad-hoc gcc gcc:lib'. 2. I thought about this. Maybe we could add a cargo subcommand that interacts with the guix/nix daemon directly [0] and then have a small cargo-build-system that wraps it. I think this would be neat because we could avoid

Re: rust work in progress conflicts

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

Re: rust work in progress conflicts

Hi ng0, all! Le Thu, 28 Jul 2016 08:28:18 +, ng0 a écrit : > ng0 writes: [...] > > So I picked up rust.scm again and forgot about this thread, only a > search for rust brought it up again. > As this will be a long task obviously, however we

Re: rust work in progress conflicts

Hi, ng0 writes: > Jelle Licht writes: > >> I have taken the liberty to try my hand at finishing this, as I figured >> it would be a good way for me to get more familiar with 'the Guix way' >> of packaging things. > > Thanks! > Also, could you please use this

Re: rust work in progress conflicts

Alex Griffin skribis: > On Thu, May 5, 2016, at 08:35 AM, Ludovic Courtès wrote: >> >> Yeah it’s OK to do it in the order: write the package bootstrapped from >> the binary blob, and then work on bootstrapping it from OCaml. > > I do not think that bootstrapping Rust from OCaml

Re: rust work in progress conflicts

On Fri 06 May 2016 11:05, Andy Wingo writes: > But given that even OCaml includes a binary blob (!), I don't think that > we can practically require bootstrapped language implementations to > bootstrap all the way. To clarify! Obviously it would be better from a

Re: rust work in progress conflicts

On Thu 05 May 2016 16:46, Alex Griffin writes: > On Thu, May 5, 2016, at 08:35 AM, Ludovic Courtès wrote: >> >> Yeah it’s OK to do it in the order: write the package bootstrapped from >> the binary blob, and then work on bootstrapping it from OCaml. > > I do not think that

Re: rust work in progress conflicts

Jelle Licht writes: > I have taken the liberty to try my hand at finishing this, as I figured > it would be a good way for me to get more familiar with 'the Guix way' > of packaging things. Thanks! Also, could you please use this email address for further CC things (I tend to

Re: rust work in progress conflicts

On Thu, May 5, 2016, at 08:35 AM, Ludovic Courtès wrote: > > Yeah it’s OK to do it in the order: write the package bootstrapped from > the binary blob, and then work on bootstrapping it from OCaml. I do not think that bootstrapping Rust from OCaml is a practical goal. When you guys have talked

Re: rust work in progress conflicts

Jelle Licht skribis: > Now there are two approaches which might make sense to me: > > 1) We package a recent stage-0 binary (thus adding yet another random > binary to the mix) This is something we want to avoid as much as possible. Part of the solution is to raise awareness

Re: rust work in progress conflicts (was: Re: LLVM: "FileCheck" is missing)

I have taken the liberty to try my hand at finishing this, as I figured it would be a good way for me to get more familiar with 'the Guix way' of packaging things. Wow, did I misjudge this rabbit hole though. It seems to be the case that rust needs the (most recent) snapshotted binary stage-0

rust work in progress conflicts (was: Re: LLVM: "FileCheck" is missing)

Here is my work in progress rust.scm, it is on pause until the next release of rust as mentioned before: ~/projects/guix_project/guix/gnu/packages $ cat rust.scm ;;; GNU Guix --- Functional package management for GNU ;;; Copyright © 2016 Nils Gillmann ;;; ;;; This file is