NixOS 16.09 released
nixos.org
NixOS 16.09 released
1–10 of 31 posts
Re: NixOS 16.09 released
#2Re: NixOS 16.09 released
#3The main issue I had while using NixOS is that it has a small and somewhat broken set of packages. This is compounded by the very incomplete Nix documentation - its way too hard to create new packages.
I think the project as a whole would welcome suggestions on where to improve docs as well, and would _definitely_ appreciate some new docs being written. It is hard to do this once you're too familiar :(.
Re: NixOS 16.09 released
#4Re: NixOS 16.09 released
#5Quick question, the url https://nixos.org/nixos/download.html lists the same url for both 32 and 64bits iso, I wonder if these are multiarch images or just an error.
Re: NixOS 16.09 released
#6Quick question, the url https://nixos.org/nixos/download.html lists the same url for both 32 and 64bits iso, I wonder if these are multiarch images or just an error.
https://github.com/NixOS/nixos-homepage/commit/70bcfbb64a0e3...
Re: NixOS 16.09 released
#7Re: NixOS 16.09 released
#8Quick question, the url https://nixos.org/nixos/download.html lists the same url for both 32 and 64bits iso, I wonder if these are multiarch images or just an error.
Re: NixOS 16.09 released
#9[0] https://github.com/NixOS/nixpkgs/issues/18995
Yeah. The devs believed it was okay to make gcc -O2 by default and impossible to override from the command line you gave to gcc.
If you encountered this issue I hope google could quickly bring you to that issue on github. Good luck and don't waste hours to figure out why.
Re: NixOS 16.09 released
#10If you found out through gdb that your code compiled with -O0 was still somehow optimized by gcc, or if you found out that your gcc did not optimize your code aggressively enough although you gave it -Ofast, check out this issue [0]. [0] https://github.com/NixOS/nixpkgs/issues/18995 Yeah. The devs believed it was okay to make gcc -O2 by default and impossible to override from the command line you gave to gcc. If you…