[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
significance of collisions in 'guix environment'?
From: |
Paul Garlick |
Subject: |
significance of collisions in 'guix environment'? |
Date: |
Tue, 08 Nov 2016 17:09:11 +0000 |
Hi All,
I am in the middle of upgrading the Gmsh package in Guix. I have cloned the Guix repository, set up a profile for development, and run bootstrap, configure and make. In setting up the build environment for Gmsh, using 'guix environmnet ...', there are surprising collision messages generated:
I do:
$ ./pre-inst-env guix environment --pure gmsh
I get:
.
.
.
warning: collision encountered: /gnu/store/m6s3bz6a2sv7015z78sfzdk5ngkzdwwg-gfortran-4.9.3/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/liblto_plugin.so.0.0.0 /gnu/store/frrj3bfbmg5vrd0flh9cf8j64h7cr2v4-gcc-4.9.3/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/liblto_plugin.so.0.0.0
warning: arbitrarily choosing /gnu/store/m6s3bz6a2sv7015z78sfzdk5ngkzdwwg-gfortran-4.9.3/libexec/gcc/x86_64-unknown-linux-gnu/4.9.3/liblto_plugin.so.0.0.0
.
.
.
There are 14 gfortran-related messages and a message regarding ld-wrapper and binutils.
How should these messages be interpreted? Could there be duplication in the package inputs?
I have noticed that Gmsh lists gfortran and lapack as propagated-inputs and lapack also lists gfortran as an input.
Regards,
Paul.
- significance of collisions in 'guix environment'?,
Paul Garlick <=