!ayCRiZriCVtuCUpeLp:nixos.org

Nix Cross Compiling

577 Members
129 Servers

Load older messages


SenderMessageTime
9 Jan 2025
@greg:thehellings.comGreg HellingsWait, no, that was me building ucrt with icu76. Trying again with 7422:51:32
@greg:thehellings.comGreg HellingsOK, yeah, this is limited to only failing on MinGW as I thought. The naughty code is behind ifdef's for MinGW, so that's expected22:53:09
@greg:thehellings.comGreg HellingsShould I prepare a limited PR for master to just rev it for mingw? Or is staging updating it everywhere in the near future?22:54:49
@k900:0upti.meK900
In reply to@greg:thehellings.com
Should I prepare a limited PR for master to just rev it for mingw? Or is staging updating it everywhere in the near future?
I would prefer the latter
22:58:32
@k900:0upti.meK900Any sort of "this obscure platform uses this other thing instead of the normal thing" conditionals explode given enough time22:58:52
@greg:thehellings.comGreg HellingsAgreed. I don't know about calling Windows obscure, but it's definitely a corner case for nixpkgs23:00:42
@k900:0upti.meK900Windows is not obscure 23:06:02
@k900:0upti.meK900MinGW is, extremely 23:06:07
10 Jan 2025
@emilazy:matrix.orgemilydon't we use MinGW for all Windows cross00:59:24
@k900:0upti.meK900
In reply to @emilazy:matrix.org
don't we use MinGW for all Windows cross
Yes, which we have very little of
07:14:40
@greg:thehellings.comGreg HellingsYes, but only with gcc on some of them. And the build failure is mingw+gcc-14+ specific. For ucrt targets we seem to use clang instead and that did not manifest the failure15:33:12
@greg:thehellings.comGreg Hellings K900: Is there any pomp and circumstance needed for submitting a PR to staging-next for that, or can I send one in? 15:48:00
@k900:0upti.meK900You want to target staging15:49:09
@k900:0upti.meK900Not staging-next15:49:10
@k900:0upti.meK900And be ready to deal with the fallout15:49:19
@greg:thehellings.comGreg HellingsAnd, I presume, a mention in the release notes is worthy for this?15:49:36
@k900:0upti.meK900Probably yes15:50:48
@emilazy:matrix.orgemily if ICU version is going to drift from what Apple tracks we should maybe reconsider coupling darwin.ICU to it. cc Randy Eckenrode 16:02:21
@k900:0upti.meK900Is darwin.ICU just the system version of ICU?16:03:05
@emilazy:matrix.orgemilyit's a source build of the version Apple ships16:03:23
@emilazy:matrix.orgemilywhich is a fork of ICU with a bunch of changes16:03:27
@emilazy:matrix.orgemilythat some packages require16:03:32
@emilazy:matrix.orgemily we switched to using it for icu this cycle but I think on kind of just a "just because" basis 16:03:43
@emilazy:matrix.orgemilythey do stay reasonably up-to-date (currently versions are synced)16:03:59
@k900:0upti.meK900I like making the environment more like native16:04:02
@k900:0upti.meK900But I also like having one version of thing in nixpkgs16:04:12
@k900:0upti.meK900Complicated16:04:17
@greg:thehellings.comGreg HellingsThe more native it stays, the less someone who builds with it needs to ship to users16:04:26
@emilazy:matrix.orgemilyindeed16:04:35
@emilazy:matrix.orgemily I think libffi = darwin.libffi is right 16:04:40

Show newer messages


Back to Room ListRoom Version: 6