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
bgamari_ has quit [Quit: ZNC 1.7.5 - https://znc.in]
bgamari has joined #nixos-dev
bgamari has quit [Client Quit]
bgamari has joined #nixos-dev
peti_ has joined #nixos-dev
bhipple has joined #nixos-dev
peti has quit [Ping timeout: 260 seconds]
bhipple has quit [Ping timeout: 260 seconds]
<emily> is there any advantage to using the API at all?
<emily> you can just rely on tarball etags I think
<emily> I wonder why Nix uses the API
<samueldr> I think there was a breakage with Etags, memories from commit messages past
<emily> I don't fully understand eelco's last reply
<samueldr> (thanks github, not opening up to the comment you linked :/)
<emily> ugh, probably because it's marked as outdated
<emily> ctrl+f github and expand them until you see talk about tarballs :p
<samueldr> once expanded, re-triggering a navigation (ctrl+L, enter) will point to it
<samueldr> hmmm, I'd need to validate, but I think it's because with the github-api-backed it saves the hash for whatever master points to, while with a tarball, there is no way to get that hash
<samueldr> saves the hash -> saves the revision ID
<samueldr> while with a tarball you can't exactly "follow master.tar.gz to ${rev}.tar.gz" as a standard thing
<samueldr> at least, for generic tarballs
<samueldr> a github-implementation-details tarball backend could maybe do something about it, not sure if the links end up giving the information
<emily> ah, I see
<samueldr> just in case, here's the line for which the conversation's attached to, https://github.com/NixOS/rfcs/pull/49/files#diff-a5a138ca225433534de8d260f225fe31R219
pxc has quit [Remote host closed the connection]
pxc has joined #nixos-dev
pxc has quit [Quit: Konversation terminated!]
<danderson> howdy. So, I just tried pulling a w64 (64-bit windows) cross-compiler into my shell.nix, and now I'm building a Windows binutils+gcc+friends from scratch on my poor wimpy laptop.
<danderson> Am I correct that this is because this toolchain isn't referenced directly from all-packages.nix, and so hydra doesn't build one?
<danderson> if I _am_ correct, would it make sense to add a reference, similar to how various arm cross-compilers are referenced already?
<danderson> not that I don't enjoy spending a couple hours building compilers, of course ;)
orivej has quit [Ping timeout: 264 seconds]
Taneb has quit [Quit: I seem to have stopped.]
Taneb has joined #nixos-dev
orivej has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
drakonis has quit [Quit: WeeChat 2.8]
drakonis has joined #nixos-dev
orivej has joined #nixos-dev
<infinisil> danderson: This might be what `limitedSupportSystems` could be used for in pkgs/top-level/release.nix
<infinisil> Hm maybe not
<infinisil> I thought this might only build stdenv, but that doesn't appear to be the case
<infinisil> I don't think hydra has the capacity to build *every* package for another platform
<danderson> so, this is *not* building packages for another platform
<danderson> it's building the gcc cross-compiler that targets windows, but x86_64-linux binaries
<danderson> just another compiler for one of the supported platforms :)
<infinisil> Ahh
<infinisil> danderson: What attribute do you use to build it?
<danderson> BpkgsCross.mingwW64.buildPackages.gcc and pkgsCross.mingw32.buildPackages.gcc
<danderson> pkgsCross attributes for other cross-compilers (e.g. x86_64-linux -> arm-linux) are referenced explicitly in all-packages.nix, so I _think_ that's why they get built+cached?
<samueldr> (it could also be because mobile-nixos depends on them)
<infinisil> I guess the main reason it doesn't build that is because `pkgsCross` doesn't use `recurseIntoAttrs`
<danderson> e.g. avrgcc = pkgsCross.avr.buildPackages.gcc;
<infinisil> danderson: Yeah you could add such an attribute to all-packages and hydra should build it
<samueldr> ah, not those though
<samueldr> I was thinking about e.g. pkgsCross.aarch64-multiplatform.buildPackages.*
justanotheruser has quit [Ping timeout: 244 seconds]
cole-h has quit [Quit: Goodbye]
thonkpod has quit [Quit: WeeChat 2.6]
alp has joined #nixos-dev
peti_ is now known as peti
justanotheruser has joined #nixos-dev
thonkpod has joined #nixos-dev
thonkpod has quit [Quit: WeeChat 2.7.1]
thonkpod has joined #nixos-dev
notgne3 has joined #nixos-dev
ryantm_ has joined #nixos-dev
garbas_ has joined #nixos-dev
m1cr0m4n has joined #nixos-dev
grw1 has joined #nixos-dev
notgne2 has quit [*.net *.split]
m1cr0man has quit [*.net *.split]
tv has quit [*.net *.split]
FireFly has quit [*.net *.split]
ryantm has quit [*.net *.split]
garbas has quit [*.net *.split]
grw has quit [*.net *.split]
tv1 has joined #nixos-dev
FireFly has joined #nixos-dev
rsa has joined #nixos-dev
__monty__ has joined #nixos-dev
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
tilpner has joined #nixos-dev
alp has quit [Ping timeout: 240 seconds]
alp has joined #nixos-dev
alp has quit [Remote host closed the connection]
alp has joined #nixos-dev
alp has quit [Remote host closed the connection]
ris has quit [Ping timeout: 258 seconds]
tilpner_ has joined #nixos-dev
tilpner has quit [Read error: Connection reset by peer]
tilpner_ is now known as tilpner
garbas_ has quit [Quit: WeeChat 2.7.1]
garbas has joined #nixos-dev
FRidh has joined #nixos-dev
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-dev
drakonis_ has joined #nixos-dev
drakonis has quit [Ping timeout: 260 seconds]
drakonis has joined #nixos-dev
drakonis_ has quit [Ping timeout: 260 seconds]
notgne3 is now known as notgne2
drakonis1 has joined #nixos-dev
drakonis has quit [Quit: WeeChat 2.7]
drakonis1 is now known as drakonis
fadenb has quit [Quit: killed]
tilpner_ has joined #nixos-dev
tilpner has quit [Ping timeout: 246 seconds]
tilpner_ is now known as tilpner
fadenb has joined #nixos-dev
fadenb has quit [Client Quit]
<sphalerite> > builtins.fetchurl { foo = null; }
<{^_^}> unsupported argument 'foo' to 'fetchurl', at 0x1b7a7d8
<sphalerite> ^ this probably shouldn't be dumping pointers in the error message?
<domenkozar[m]> that's fixed in master
<sphalerite> ah cool
fadenb has joined #nixos-dev
fadenb has quit [Client Quit]
fadenb has joined #nixos-dev
fadenb has quit [Quit: killed]
orivej has quit [Ping timeout: 256 seconds]
fadenb has joined #nixos-dev
fadenb has quit [Client Quit]
orivej has joined #nixos-dev
peti has quit [Quit: WeeChat 2.8]
cole-h has joined #nixos-dev
Jackneill has quit [Ping timeout: 260 seconds]
Jackneill has joined #nixos-dev
justanotheruser has quit [Ping timeout: 265 seconds]
orivej has quit [Ping timeout: 240 seconds]
orivej_ has joined #nixos-dev
justanotheruser has joined #nixos-dev
orivej_ has quit [Ping timeout: 260 seconds]
MichaelRaskin has quit [Read error: Connection reset by peer]
MichaelRaskin has joined #nixos-dev
FRidh has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-dev
alp has joined #nixos-dev
bridge[evilred] has quit [Remote host closed the connection]
bridge[evilred] has joined #nixos-dev
red[evilred] has joined #nixos-dev
ris has joined #nixos-dev
<LnL> FYI some of the ofborg infrastructure is down so evaluations and builds will be stalled for a bit
Raito_Bezarius has quit [Read error: Connection reset by peer]
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has joined #nixos-dev
Raito_Bezarius has quit [Changing host]
<yorick> Mic92: I'm trying to cross-compile python3Packages.pillow for the raspberry pi (on 20.03), and getting "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
<yorick> do you have any quick idea on how to solve this?
<yorick> you seem to have worked on that on btrfs-tools
<yorick> I do have _PYTHON_HOST_PLATFORM set to armv7l-unknown-linux-gnueabihf
teto has joined #nixos-dev
<yorick> I worked around it with export CFLAGS="$CFLAGS -I ${self.python}/include/python3.7m"
<yorick> (and something similar for ldshared)
teto has quit [Ping timeout: 252 seconds]
<Mic92> yorick: I don't particulary remember this error but could be the reason that you have a 64-bit python that has the wrong definition for your 32-bit armv7?
<Mic92> I was mainly doing aarch64 which has the same word length as x86_64 so I might have not encountered that error.
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
teto has joined #nixos-dev
FRidh has quit [Quit: Konversation terminated!]
alp has quit [Ping timeout: 244 seconds]
alp has joined #nixos-dev
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
teto has quit [Quit: WeeChat 2.8]
__monty__ has quit [Quit: Nuh uh uh, zaeph : p]
<{^_^}> firing: BuildsStuckOverTwoDays: https://status.nixos.org/prometheus/alerts
alp has quit [Ping timeout: 272 seconds]
bhipple has joined #nixos-dev
risson has quit [Quit: pouet]
risson has joined #nixos-dev
makefu has quit [Quit: WeeChat 2.6]
makefu has joined #nixos-dev
bhipple has quit [Remote host closed the connection]