Re: create a symlink

2019-03-07 Thread Rene
Hello Danny, sorry for delay. I have updated my repository with commit dc7d6d4ece30c7ab25e9f1927d64f2b409ab896c(version 14). Danny Milosavljevic writes: > are you sure you put the call into guix/scripts/system.scm ? > > There are a lot of #$ things there already - should work. > > In gnu/build

Re: librsvg & Rust

2019-03-07 Thread Danny Milosavljevic
Hi, On Fri, 8 Mar 2019 02:52:05 +0100 Danny Milosavljevic wrote: > > On hydra.gnu.org, our rust packages can only successfully be built on > > x86_64-linux. They fail to build on i686-linux and armhf-linux. I > > don't know about aarch64-linux. Could we link to the hydra pages containing th

Re: librsvg & Rust

2019-03-07 Thread Danny Milosavljevic
Hi Mark, On Wed, 06 Mar 2019 18:55:18 -0500 Mark H Weaver wrote: > Marius Bakke writes: > > I wanted to ask about this: is Rust supported on all the platforms we > > support at the moment? > > On hydra.gnu.org, our rust packages can only successfully be built on > x86_64-linux. They fail to

Using hwloc 2.0.3 in openmpi

2019-03-07 Thread Ricardo Wurmus
Hi Guix, currently, the openmpi package is built with hwloc 1.11.12, which includes this note: ;; Note: For now we keep 1.x as the default because many packages have yet ;; to migrate to 2.0. OpenMPI does work with hwloc 2.0, though, and I’ve built it successfully after replacing “hwloc” wit

Re: librsvg & Rust

2019-03-07 Thread Efraim Flashner
On Wed, Mar 06, 2019 at 06:55:18PM -0500, Mark H Weaver wrote: > Marius Bakke writes: > > I wanted to ask about this: is Rust supported on all the platforms we > > support at the moment? > > On hydra.gnu.org, our rust packages can only successfully be built on > x86_64-linux. They fail to build

Splitting mkvtoolnix outputs: cycle detected in the references

2019-03-07 Thread Pierre Neidhardt
Hi! I'm trying to split mkvtoolnix-gui (depends on Qt) to a separate "gui" output. "out" would only contain the command line tools. Disabling Qt shrinks the closure size from 1.5+ GB to 277 MB. Pretty neat, huh? :) I naively tried to move mkvtoolnix-gui to the "gui" output: --8<---

Re: Guix system cross-compile

2019-03-07 Thread Hartmut Goebel
Am 07.03.19 um 15:44 schrieb Mathieu Othacehe: > --system means try to build natively for the specified architecture. It > is possible on the arch that support multiple personalities (i686 and > x86 for instance), or using QEMU binfmt_misc mechanism. The argument > is an arch name like "x86_6

Re: Guix system cross-compile

2019-03-07 Thread Mathieu Othacehe
Hi Alex, This subject is explained in "Package Transformation Options" section of the documentation. In short: --system means try to build natively for the specified architecture. It is possible on the arch that support multiple personalities (i686 and x86 for instance), or using QEMU binfm

Re: Guix system cross-compile

2019-03-07 Thread Ricardo Wurmus
Alex Vong writes: > As a related question, I'm curious what's the difference between > "guix build --target ..." vs "guix build --system ..."? “--target” is for cross-compilation. “--system” is for using a different persona (e.g. i686 on an x86_64 system). > Is it possible that one command r

Re: Guix system cross-compile

2019-03-07 Thread Alex Vong
Hello everyone, As a related question, I'm curious what's the difference between "guix build --target ..." vs "guix build --system ..."? Is it possible that one command results in build failure but the other command doesn't? Cheers, Alex Mathieu Othacehe writes: > Hello, > > I'm digging up the