zimoun <zimon.touto...@gmail.com> writes: > However, is it expected that LIBRARY_PATH is not set? > > --8<---------------cut here---------------start------------->8--- > $ cat /tmp/proto/etc/profile > # Source this file to define all the relevant environment variables in Bash > # for this profile. You may want to define the 'GUIX_PROFILE' environment > # variable to point to the "visible" name of the profile, like this: > # > # GUIX_PROFILE=/path/to/profile ; \ > # source /path/to/profile/etc/profile > # > # When GUIX_PROFILE is undefined, the various environment variables refer > # to this specific profile generation. > > export > PATH="${GUIX_PROFILE:-/gnu/store/m26p44mxy4k79gzy18nq2nivygrdmkm5-profile}/bin${PATH:+:}$PATH" > --8<---------------cut here---------------end--------------->8---
LIBRARY_PATH is only set if you include 'gcc' or 'gcc-toolchain' in the profile, and is generally only needed if you want to compile something. >> I think there were proposals to start using a 'dev' output for headers >> and such, but don't know if it got anywhere. > > Moreover, the static libraries are also installed with simply > "protobuf@2.6.0:out". I can't find a protobuf@2.6.0 package, but at least for 2.6.1 there are no .a files in the default output. > I have tried to adapt the definition of protobuf adding a "lib" flag. > But it fails with "cycle detected in the references of". Roptat > explained on IRC how to track the issue and before investigating some > time, I would like to be sure to well understand. :-) The cyclic reference means something in the lib output references "out". To find out which, try grepping for the store hash of the "out" output. HTH, Marius
signature.asc
Description: PGP signature