Closed drewc closed 7 months ago
Name | Link |
---|---|
Latest commit | bd2c17c677db4e9b4a1999cde110e5928b3892e4 |
Latest deploy log | https://app.netlify.com/sites/elastic-ritchie-8f47f9/deploys/656d63461a434f0008fa5ef7 |
Deploy Preview | https://deploy-preview-1062--elastic-ritchie-8f47f9.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
1. Is make core working for you? Somehow I had to `make bootstrap && make from-scratch` instead in Nixpkgs.
Yes, it's now working fine. For 0.17 I had to build the bootstrap, package that, build gambit, package that, then build.sh gerbil with those deps.
Now it seems to work just by the three steps. However I have not tried to build on all my guix boxes from scratch so it may be working by fluke. I'll make sure.
2. Shouldn't you be replacing the `"gcc"` by a hermetic link to a static gcc, as I do in Nixpkgs?
I'm not sure that's needed.
3. Shouldn't you use `--enable-march=` to avoid non-portable instructions on a public package?
I thought that march-native was to enable mass gcc optimizations? The package is built with gcc on a GNU system. Where did I go wrong?
--enable-march=native
will work better on the same (kind of) machine that compiles it, at the expense of not working on other machines. So if you have a fancy recent Intel64 CPU, the binary won't run on an old AMD64 CPU, and vice versa.
This works as described in the readme. Should add some toplevel install docs but for 0.18.1 it's fine as is.