Paul Garlick <[email protected]> skribis: > $ ./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?
They are harmless in this case: we purposefully want ld-wrapper to override binutils, and the gfortran/gcc collisions have no effect. So you can safely keep going. :-) However, these messages are clearly suboptimal, precisely because as a user one doesn’t what to do with them. There are ideas about avoiding these messages and instead getting a proper error when there are really problematic collisions (for instance, collisions due to two different versions of a package ending up in the profile.) HTH! Ludo’.
