<clever>
ah, is there a way to save the compile output?
<clever>
deba5e12: just run "nix-shell -p libpcap" and then try to compile under that
<clever>
and there is a lot of other things nix-shell does to help
<clever>
that tells it where to look at runtime, but not where to look at link-time
<clever>
deba5e12: it will never look in ~/.nix-profile by default
<clever>
deba5e12: nix only sets the linker flags up if your using nix-build or nix-shell
<clever>
apeyroux: does it do anything with emacs?
<clever>
i would just check to see where the symlink points after it gives the warning, and it should stay pointing in that direction
<clever>
simukis: in the case of systemPackages, it will ignore the collisions, so i believe it will depend on the order of the entires within systemPackages
<clever>
simukis: what package provides the original executable?
<clever>
srhb: qemu can also embed a tftp server inside the userland nat for you
<clever>
and it needs zero config
<clever>
so the guests can get internet access without having to give qemu root
<clever>
then it opens a normal tcp connection on the host, and sends it to linux, which re-packetizes it
<clever>
the userland nat in qemu will decode packets the guest tries to send out, and turn them into a simple bytestream
<clever>
s/scribe/script/
<clever>
srhb: "bridge helper failed" implies that qemu is supposed to be running a scribe to deal with bridging, if you dont need very fast network, you can just omit -netdev entirely, and qemu should setup userland nat
<clever>
srhb: and if you want it to get into the internet, you also need to add the main ethernet card to that bridge in the nixos config
<clever>
srhb: 'ip link' should show what bridge things have been enslaved to
<clever>
and this allows different programs to depend on different libc's
<clever>
everything on nix has an rpath set, which contains the absolute paths for things like libc
<clever>
Rodenbach: anything compiled by nix expects LD_LIBRARY_PATH to either be blank, or to contain the opengl drivers
<clever>
that looks normal at a glance
<clever>
nix-shell '<nixpkgs>' -A gzdoom then run genericBuild
<clever>
ah
<clever>
nix doesnt allow you to use things you manualy built long-term
<clever>
drakonis: for testing, or to use the built product?
<clever>
there should be an option for that somewhere in the kde gui
<clever>
drakonis: gzdoom lacks a .desktop file, you have to manualy run gzdoom in a terminal, or create a shortcut that runs gzdoom
<clever>
drakonis: how are you installing them, and looking for them?
<clever>
there is an open issue about it deleting things sooner in the process
<clever>
mbrgm: you need to gc, then do another deploy, and maybe delete one of them by hand
<clever>
mbrgm: ah, systemd-boot doesnt have a limit, you can only GC things
<clever>
mbrgm: oops, see above
<clever>
makefu: boot.loader.grub.configurationLimit can be used to limit how many generations are actually put into /boot, seperate from garbage collecting them
<clever>
makefu: grub or efi?
<clever>
makefu: look at the man page for nix-collect-garbage, the --delete-older-than options
<clever>
systemPackages means you can keep track of stuff you installed by tracking configuration.nix in git
<clever>
its mostly preference which one you use
<clever>
nix-env is for more imperative installations
<clever>
WinterFox[m]: or nix-env -iA nixos.firefox
<clever>
WinterFox[m]: either add it to environment.systemPackages in configuration.nix and nixos-rebuild
<clever>
makefu: feel free to bounce questions off me if you want to fill more things on the wiki in
<clever>
simpson: oh, thats your own question? heh
<clever>
simpson: fuse passes struct's over the open file handle, to implement the api, and if you know the format, you could re-implement libfuse in any language
<clever>
simpson: but modprobe was never meant to be used in a setuid context, and obeyed env varaibles, causing an exploit
<clever>
simpson: i also recently saw an exploit in fuse, where it would automaticaly "modprobe fuse", from a setuid root binary
<clever>
zetok: and the rdm that sphalerite mentioned is in rust
<clever>
zetok: hsdm is in haskell
<clever>
Infinisil: basicaly, it will launch X, then connect to X and present a login screen (optionaly with shutdown/reboot buttons), and once you give valid credentials, it will drop root to that user, and execute a desktop manager
<clever>
sphalerite: more like getty + startx in a single binary, with no shell in the middle
<clever>
i recently thought about cheating a bit, and doing the entire gui in textmode, then spawning X after you auth
<clever>
pie__: ah, that explains how you wound up with a 32bit version
<clever>
pie__: what nix expression are you using?
<clever>
pie__: the result/bin/mist made by compiling the nix expression, oh wait, thats miko___'s expression
<clever>
pie__: what if you run ldd on the built mist file?
<clever>
pie__: it should default to the same arch as the nix binary, what does this say? nix-instantiate --eval -E builtins.currentSystem
<clever>
pie__: yeah, you have a 32bit file in the commented out fetchurl, but a 64bit file in the src attribute
<clever>
Guillaum: that sounds related
<clever>
Guillaum: doesnt sound like it would cause the timer issues
<clever>
Guillaum: anything interesting in dmesg?
<clever>
miko___: and the full error message it gave?
<clever>
miko___: can you gist the nix expression you have?
<clever>
yeah, the lib you want is in gtk2
<clever>
--set-rpath ${lib.makeLibraryPath [ gtk2 ]} i think
<clever>
--set-rpath for patchelf
<clever>
ah, then you need to add gtk to the rpath
<clever>
miko___: is it saying file not found when you run the file in bin?
<clever>
juselius: overrideDerivation normally takes a function, that will return an attrset of new values, but callPackage makes an entirely new derivation
<clever>
juselius: and overrideDerivation doesnt work like that
<clever>
juselius: your also importing a 2nd nixpkgs, which uses different config and can cause any number of weird things
<clever>
juselius: line 4 replaces the entire linuxPackages attrset with a set containing only virtualboxGuestAdditions
<clever>
juselius: yep, exactly what i helped somebody with just ~4 hours ago
<clever>
drakonis: by default, nixpkgs will load ~/.config/nixpkgs/config.nix, but nixos forces it to use the nixpkgs.config attrset from the nixos config, and only for the pkgs passed to configuration.nix
<clever>
you beat me by 1 second!
<clever>
miko___: add unzip to the buildInputs
<clever>
juselius: can you gist the nix files you changed?
<clever>
gchristensen: yeah, i always see people either bumping it on update (which breaks what it was meant to fix), or thinking that changing it can update everything
<clever>
shnupta: networking.wireless.enable = true; in the configuration.nix, and there is "nixos-install --chroot" on the installer, where you can then do "nixos-rebuild boot"