I'm trying to use grpc (http://www.grpc.io/) from ruby. This gem has some
hardcoded paths in there, and apparently also tries to write to a directory
owned by the ruby interpreter after building a native extension. I've
opened a issue for this at https://github.com/grpc/grpc/issues/8935
2016-12-0
Yes that's it. There is also a pkgs.defaultGemConfig that contains common
overrides, like injecting libxml for the nokogiri gem. You might want to
merge it with your override (or submit yours to nixpkgs).
On Thu, 1 Dec 2016, 20:51 Maarten Hoogendoorn, wrote:
> OK, I found a solution after taking
OK, I found a solution after taking a longer look at the bundlerEnv
implementation.
Each gem is packaged as a separate derivation (which makes complete sense).
BundlerEnv offers the `gemConfig', in which one can set another postInstall
step.
In my case, the following snippet works:
with pkgs; (bu
Hi,
I'm trying to build a gem that has vendored a statically compiled program
(that still depends on /lib64/ld-linux-x86-64.so.2).
I've tried to use patchelf in the postBuild in a bundlerEnv, but it's
complaining about not having write permissions to $out
I wrote a one-liner to check for .nix fi
