| 12 Aug 2025 |
emily | (of course ideally it would support the flags) | 20:52:36 |
connor (burnt/out) (UTC-8) | Any references for prior art for how to do that, or recommendations for where such a wrapper would go? | 20:54:34 |
emily | are you using cc-wrapper already? | 20:58:25 |
Grimmauld (any/all) | there is already flags being filtered, e.g. -march flag will be dropped | 21:01:45 |
| 17 Aug 2025 |
| Benno Fünfstück joined the room. | 17:51:29 |
| 19 Aug 2025 |
emily | does anyone know if configurePlatforms = [ "host" ]; by default would break as much stuff as [ "build" "host" ] | 21:33:56 |
Alex | In reply to @emilazy:matrix.org does anyone know if configurePlatforms = [ "host" ]; by default would break as much stuff as [ "build" "host" ] Wouldn't this break cross for most packages?
Looking at the autoconf documentation, it seems like it won't try to guess the build platform if you set --host. | 22:39:43 |
emily | we pass [ "build" "host" ] when doing cross | 22:40:01 |
emily | I'm just talking about the default for the native case | 22:40:05 |
emily | which should be [ "build" "host" ], but isn't because some stuff breaks | 22:40:15 |
emily | though maybe it's about time to just throw that in a cycle and deal with the fallout | 22:41:53 |
emily | I forget what Artturin said last time I was talking about a good ordering for these things | 22:42:06 |
emily | not sure if https://github.com/NixOS/nixpkgs/pull/181724 ended up resolved | 22:43:07 |
emily | ok, yeah, https://github.com/NixOS/nixpkgs/issues/178802 | 22:52:39 |
emily | I think adding wrapped prefixed compilers was the first sensible step | 22:52:45 |
emily | not sure if --host without --build would trigger such problems though | 22:52:53 |
emily | oh, it looks like we no longer re-export the prefixed ones from the wrapped packages | 22:59:19 |
emily | so maybe that's okay. | 22:59:21 |
| 20 Aug 2025 |
| jopejoe1 (4094@39c3) changed their display name from jopejoe1 (4094@GPN23) to jopejoe1. | 18:50:45 |
| 21 Aug 2025 |
| Theo Paris joined the room. | 22:11:07 |
| 23 Aug 2025 |
John Ericson | emily: https://clang.llvm.org/docs/Multilib.html oh ok, it looks like this YAML is the proper way to make a multi-target wrapped compiler | 00:36:49 |
emily | that's for multilib variants of a single architecture? which is quite different | 00:37:35 |
emily | the configuration files already support multi-target | 00:38:02 |
John Ericson | emily: do the cfg file support -m flags etc afffecting which set of lookup paths it uses? | 00:38:46 |
emily | the config files support arbitrary flags | 00:38:58 |
emily | (that's all they support) | 00:39:00 |
John Ericson | emily: err so as I interpret this is a way to do something like "if the user specifies --target=..... then inject -L ....." | 00:59:53 |
John Ericson | not just a static set of flags | 01:00:00 |
emily | but config files already offer that? they key on the target | 01:00:11 |
John Ericson | the the conditions are more semantic than syntactic | 01:00:11 |