worldofpeace_ changed the topic of #nixos-dev to: #nixos-dev NixOS Development (#nixos for questions) | NixOS stable: 20.03 ✨ https://discourse.nixos.org/t/nixos-20-03-release/6785 | https://hydra.nixos.org/jobset/nixos/trunk-combined https://channels.nix.gsc.io/graph.html | https://r13y.com | 19.09 RMs: disasm, sphalerite; 20.03: worldofpeace, disasm | https://logs.nix.samueldr.com/nixos-dev
teto has quit [Quit: WeeChat 2.8]
<clever> nbp: are you available to help with some rust->windows cross issues?
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.8]
drakonis_ has quit [Quit: WeeChat 2.7]
drakonis has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.7]
drakonis has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
drakonis has joined #nixos-dev
alp has joined #nixos-dev
cole-h has quit [Quit: Goodbye]
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Read error: Connection reset by peer]
drakonis1 has joined #nixos-dev
drakonis_ has quit [Ping timeout: 265 seconds]
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 272 seconds]
alp has quit [Ping timeout: 252 seconds]
alp has joined #nixos-dev
__monty__ has joined #nixos-dev
<nbp> clever: I never tried … so I am probably not the right person. A part from that, I can mimic M-x doctor for you.
alp has quit [Remote host closed the connection]
edef has quit [Ping timeout: 260 seconds]
edef has joined #nixos-dev
teto has joined #nixos-dev
alp has joined #nixos-dev
teto has quit [Quit: WeeChat 2.8]
teto has joined #nixos-dev
<pie_> xpost, interesting engineering retro http://neugierig.org/software/blog/2020/05/ninja.html
<yorick> so makeWrapper sounds like it should be in nativeBuildInputs
<yorick> but the only effect that has is setting the shell wrong
<yorick> should it be in buildInputs, with the hope that it never becomes something other than a shell script?
<jtojnar> yorick hmm, that sounds like a bug
<yorick> jtojnar: pkgs.runtimeShell might be wrong
<yorick> jtojnar: can you go from a native package back to the cross packages set?
<jtojnar> the way it is inserted would prevent splicing
<jtojnar> but we would not want it anyway
<jtojnar> I think
<yorick> makeWrapper = makeSetupHook { deps = [ dieHook ]; substitutions = { shell = pkgs.runtimeShell; }; } .../make-wrapper.sh
<{^_^}> #50244 (by tathougies, 1 year ago, merged): make-wrapper should use runtimeShell, not $SHELL, for cross-compilation
<yorick> okay, so runtimeShell isn't set?!
<yorick> pkgsCross.armv7l-hf-multiplatform.buildPackages.runtimeShell
<jtojnar> if I understand the cross things correcltly, it would use the bash from the package set you use
<jtojnar> since it does not splice
<yorick> what do you mean by splice?
<jtojnar> > pkgsCross.armv7l-hf-multiplatform.buildPackages.runtimeShellPackage.system
<{^_^}> "x86_64-linux"
<yorick> that doesn't seem like the intention but it happens even on that pr directly
<jtojnar> ,splicing yorick
<yorick> jtojnar: argh
<yorick> also hooray
<jtojnar> I still do not understand how all of this ties together
<gchristensen> divio's documentation blog post became a whole Thing: https://documentation.divio.com/
<jtojnar> From my understanding, building packages under pkgsCross.armv7l-hf-multiplatform uses the following triplet (x86_64-linux, armv7l-linux, armv7l-linux)
<jtojnar> and the expression will use makeWrapper from (*, x86_64-linux, armv7l-linux) (since it is nativeBuildInputs)
<jtojnar> so that would use bash from (*, x86_64-linux, armv7l-linux) as well
<jtojnar> Ericson2314 will know more about how this is supposed to work
<jtojnar> but to me, it just looks like makeWrapper was not made with cross-compilation in mind
<jtojnar> And https://github.com/NixOS/nixpkgs/pull/50244 made it somewhat work, if you stuck it into buildInputs
<{^_^}> #50244 (by tathougies, 1 year ago, merged): make-wrapper should use runtimeShell, not $SHELL, for cross-compilation
MichaelRaskin has quit [Ping timeout: 264 seconds]
teto has quit [Ping timeout: 240 seconds]
teto has joined #nixos-dev
MichaelRaskin has joined #nixos-dev
<LnL> gchristensen: "your project probably lacks an adequate tutorial"
<LnL> we have a (mostly) tutorial for intermediate users, does that count?
drakonis has joined #nixos-dev
<gchristensen> maybe? :)
<abathur> I can't remember if I'd stumbled on that, but I came to a very similar conclusion working on docs for another project, good to see this now actually
drakonis1 has quit [Ping timeout: 260 seconds]
<LnL> was referring to the nix pills
<abathur> though I struggle a little bit with whether the average person who hasn't tried to think about documentation has a strong sense that a guide and a tutorial aren't just synonyms
drakonis1 has joined #nixos-dev
drakonis has quit [Ping timeout: 260 seconds]
drakonis_ has joined #nixos-dev
<abathur> another problem on top of this but similar is when a project has one set of docs, in one doc directory, but is trying to meet the needs of multiple audiences at once
<abathur> most commonly people developing the thing itself, and people just using the thing
justanotheruser has quit [Ping timeout: 244 seconds]
<LnL> not sure that really matters, if a user is trying to solve a problem they'll probably end up in the howtos by searching
<abathur> but when the thing is also a server there can be other classes of people trying to install/secure/administrate it
<abathur> perhaps, but if a user who really needs a tutorial before they use a howto wanders in
<abathur> and the howto doesn't solve all problems
<abathur> user ends up on IRC or a forum asking fundamental questions
<abathur> haven't ever come up with more clear names, though; in that sense it may not really matter :)
nschoe has joined #nixos-dev
<abathur> I've thought (not Nix-specifically) it'd be nice to come up with some norms/patterns to succinctly communicate the baseline knowledge assumed along with an actionable pointer to where to learn them
nschoe has quit [Remote host closed the connection]
nschoe has joined #nixos-dev
cole-h has joined #nixos-dev
<abathur> I guess I'm also tempted to call out some stuff like quickrefs/cheat-sheets/glossaries as a separate type because it makes it more obvious where they're missing
<abathur> e.g. every language should have some sort of terse reference to all of the identifiers and tokens in the language that at least names them so that people can figure out what they're trying to search for information on, if not link to a reference for each
<abathur> there's a whole sad genre of question, usually following a futile search, for some fundamental information like, "what does this ungoogleable combination of symbols do?"
teto has quit [Ping timeout: 240 seconds]
dongcarl has quit [Quit: Ping timeout (120 seconds)]
dongcarl has joined #nixos-dev
justanotheruser has joined #nixos-dev
teto has joined #nixos-dev
Mic92 has quit [Quit: WeeChat 2.8]
Mic92 has joined #nixos-dev
alp has quit [Ping timeout: 244 seconds]
janneke has quit [Quit: janneke quits Mes'sing]
janneke has joined #nixos-dev
alp has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 265 seconds]
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 244 seconds]
worldofpeace_ has joined #nixos-dev
orivej_ has quit [Ping timeout: 256 seconds]
evanjs has quit [Quit: ZNC 1.7.5 - https://znc.in]
evanjs has joined #nixos-dev
orivej has joined #nixos-dev
worldofpeace_ has quit [Quit: worldofpeace_]
<clever> nschoe: error: Error loading target specification: Could not find specification for target "x86_64-pc-mingw32"
<clever> oops
<clever> nbp: ^
<clever> error: Error loading target specification: Could not find specification for target "x86_64-w64-mingw32"
<clever> nbp: depending on the nixpkgs rev, i get one of the above errors
<nbp> clever: with the rust overlay?
<clever> nbp: with naersk
<clever> let me grab the expr
<nbp> what does --show-trace gives you?
<nbp> the last lines.
<clever> nbp: its a build-time failure, after an hour of building rustc
<clever> builder for '/nix/store/wic5qj6v1q3db40iagwxlpv5g8ffcl2v-rustc-1.37.0.drv' failed with exit code 2; last 10 log lines:
<clever> error: Error loading target specification: Could not find specification for target "x86_64-w64-mingw32"
<clever> cannot build derivation '/nix/store/cxwgiwwp4c9i0p709n44aglkrsgafni8-rust-workspace-unknown-x86_64-w64-mingw32.drv': 1 dependencies couldn't be built
<nbp> clever: https://github.com/mozilla/nixpkgs-mozilla/blob/master/rust-overlay.nix#L53-L67 This is what is supported by the Rust overlay.
<clever> nbp: i do also notice, that the rust overlay is in our default.nix, but not in the overlays list
<nbp> clever: it is included with nixpkgsMozilla
<nbp> clever: Could you copy the overlay locally and add `system: __trace system {` at this location: https://github.com/mozilla/nixpkgs-mozilla/blob/master/rust-overlay.nix#L54 ?
<clever> i added the overlay, and i think its doing something
<clever> will see in a bit what its done
<nbp> clever: I never tested the windows side to be honest, it just correct-ish.
<clever> nixpkgs master was completely broken when pc got changed to w64
<nbp> felt correct-ish
<clever> i tried patching nixpkgs to just tell rust its still a pc
<clever> but then it fails due to -lphtread not being found
<nbp> clever: looking at rustup does not show any mingw32: https://github.com/rust-lang/rustup/blob/master/src/dist/dist.rs#L77-L135
<nbp> nor w64 either.
<clever> maybe id have better luck with 32bit?
<nbp> clever: I admit I failed to see what produce this error message yet.
<clever> i have confirmed that the supported target list wants pc, not gnu
<clever> ive been trying a wide range of nixpkgs revs, to try and find when it still worked
<clever> so the errors are wildly different as well
<nbp> clever: This is strange the builder seems to imply that it would fail to build rust, while the second error message seems to imply that it fails building with Rust.
<clever> i think its building a cross-rust with rust
<nbp> clever: I presume something is naming a derivation `rust`, while not building Rust but building with rust, and even cross compiling with `--target`
<clever> i did confirm its the rust package in nixpkgs that is failing
<clever> i had changed the name to nixpkgs-rust, and i think it was in rustc.nix
<nbp> clever: so maybe this is an error in Nixpkgs, have you tried the overlay (by luck) https://github.com/nmattia/naersk#using-naersk-with-nixpkgs-mozilla ?
<clever> oh, and theres a secondary problem
<clever> building rustc completely hangs chrome
<clever> but ghc has never done that
<clever> how is rustc consuming even more cpu? lol
<nbp> :cough: use Firefox :P
<clever> i used to use firefox more, but when it took 4gig of ram to even start (tab addict), i had to switch
<clever> also, firefox banning old style extensions and forcing several features to be ditched has turned me away a bit
<clever> along with the signing requirements
<nbp> We should have lazy-loading tabs by default now.
<clever> but the extension i wrote wont load, and mozilla refuses to even sign it for updates
<clever> because its using the old api
<nbp> since a while, so just restarting Firefox should help. Or use an addon to unload tabs.
<clever> and the new api doesnt have the features i need, so i cant port it
<nbp> The old API is still present, except that features are being removed everyday. But we still have legacy addon for running our test suite.
<nbp> (However, I do not recall how to add them)
<clever> firefox refuses to even load an addon enless its been signed by mozilla, and moz wont sign legacy addons
<nbp> Now they are called system-addons
<clever> sqlite and xul sidebars are the main things i think id loose
<clever> and there is a large xpc? component in the bg, that manages all state
<nbp> anyway … I will look what give the wrong --target, and try to replace it by one which is listed in rust-up.
<clever> the overlay from that readme does look like it would help as well
<nbp> ^ I suggest, I will not as I have not tried on windows.
* nbp off …
orivej_ has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
alp has quit [Ping timeout: 272 seconds]
orivej_ has quit [Ping timeout: 246 seconds]
<clever> builder for '/nix/store/dlbq708yz2g6y2qq6bi5qvrrfgacmkhz-rust-workspace-deps-unknown-x86_64-w64-mingw32.drv' failed with exit code 1; last 20 log lines:
<clever> error: linker `cc` not found
<clever> nbp: with the overlay you linked, it now fails to even find a compiler/linker
alp has joined #nixos-dev
ryantm_ is now known as ryantm
Gaelan has joined #nixos-dev
<infinisil> Is it possible to run a web server within a derivation build that catches all network requests and can give some meaningful answer?
<qyliss> catching all network requests is almost certainly not possible
<qyliss> your best bet for that could be LD_LIBRARY_PATH, but it would be horrible
<qyliss> LD_PRELOAD, rather
<infinisil> Hm, I guess I could patch the source of the thing that fetches to use localhost
<infinisil> I guess that's not too bad
<MichaelRaskin> You can just use lighttpd as a proxy
<MichaelRaskin> Lighttpd serves the files given
<MichaelRaskin> Proxy requests are usable as normal HTTP/1.1 requests.
mmlb has quit [Read error: Connection reset by peer]
nschoe has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
<MichaelRaskin> If your build supports http_proxy, that is…
<MichaelRaskin> Hmm, it might not agree to use it http_proxy and want HTTPS CONNECT, though
mmlb has joined #nixos-dev
lukegb has quit [Ping timeout: 258 seconds]
<infinisil> I think I might just try a bit harder to not have to do that
<MichaelRaskin> Although of course squid has SSL bumping
<MichaelRaskin> But replacing everything with http://localhost/old.domain.name/… sounds better indeed
lukegb has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis_ has quit [Read error: Connection reset by peer]
drakonis has quit [Read error: Connection reset by peer]
drakonis2 has joined #nixos-dev
drakonis has joined #nixos-dev
drakonis2 has quit [Ping timeout: 265 seconds]
alp has quit [Ping timeout: 244 seconds]
<infinisil> MichaelRaskin: That sounds like a decent idea if nothing else works
<MichaelRaskin> Of course if you can just put the files where the build expects them, it's much better, not objections here
evanjs has quit [Read error: Connection reset by peer]
<infinisil> Yeah
evanjs has joined #nixos-dev
evanjs has quit [Ping timeout: 256 seconds]
evanjs has joined #nixos-dev
__monty__ has quit [Quit: leaving]
alp has joined #nixos-dev
justanotheruser has quit [Quit: WeeChat 2.7.1]
justanotheruser has joined #nixos-dev
alp has quit [Ping timeout: 265 seconds]
alp has joined #nixos-dev
<julm> TIL, https://lazamar.co.uk/nix-versions/ Find all versions of a package that were available in a channel and the revision you can download it from.
harrow has quit [Quit: Leaving]
bridge[evilred] has quit [Remote host closed the connection]
bridge[evilred] has joined #nixos-dev
red[evilred] has joined #nixos-dev
justanotheruser has quit [Ping timeout: 258 seconds]