Explore >> Select a destination
|
You are here 
|
hoverbear.org | ||
| | | | |
myme.no
|
|
| | | | | ||
| | | | |
blog.dbalan.in
|
|
| | | | | [AI summary] The post details the process of configuring a Mac using Nix and Nix-Darwin, including setting up system packages, managing Homebrew with Nix, and creating a declarative configuration for consistent development environments. | |
| | | | |
blog.arkadi.one
|
|
| | | | | As I fall down the NixOS rabbit hole, this is a reference page for me. This is base install of GNOME NixOS from my Acer laptop. # Edit this configuration file to define what should be installed on # your system. Help is available in the configuration.nix(5) man page # and in the NixOS manual (accessible by running 'nixos-help'). { config, pkgs, ... }: { imports = [ # Include the results of the hardware scan. | |
| | | | |
nguyenhuythanh.com
|
|
| | | I think everyone who uses NixOS should have encountered this dreaded error (I'm using a "random" binary file that comes from Codeium, which is an code completion extension powered by AI): ./language_server_linux_x64 # zsh: no such file or directory: ./language_server_linux_x64 It is quite elusive on why does this happen. After taking a while searching and reading, I "sort of" understood the problem, but can only put it to my terms like this: in other OSes (Ubuntu for example), C libraries can be found using a global PATH, while NixOS does not have the same semantic; it leads to the problem that compiled binaries cannot find the C libraries they need. | ||
