Jaime Fournier
Jaime Fournier
With latest gambit 4.8.9 built and installed, the following is the build log. https://gist.github.com/ober/b943723f97002ee8e88e92c7ec3b6fe8
/src # gxpkg build ... build in current directory *** ERROR IN gerbil/tools/gxpkg#pkg-manifest! -- No such file or directory (call-with-input-file "/src/.gerbil/pkg/github.com/mighty-gerbils/gerbil-libyaml.manifest" '#) --- continuation backtrace: [0] ##primordial-exception-handler-hook [1] gerbil/tools/gxpkg#pkg-manifest! [2]...
Currently our packages install to /opt/gerbil. As /opt/gerbil/bin is not in the default PATH, we need to add symlinks to /usr/bin for /opt/gerbil/bin binaries. Additionally we need to validate that...
If you have a build that fails, or is interrupted, it can't be continued with `make` as it just exits.
Fall back to using the meta-data interface to fill in credential information if none is provided. This will allow users to invoke AWS calls via say the sqs shard without...
Setup an additional tag for master to point to the latest sha.