00:02:56 i really need to yeet the rest of the perl stuff in the build (tools might be a bit longer)... 00:03:35 i know for me, like 90% of my build failures are update bumped perl minor version and I didn't notice until an hour later 18:32:33 For illumos builds on Helios we have a tool that generates the right environment file, which I think has helped a lot 18:32:53 (whether you delete the perl or not, I think it's valuable) 18:33:02 I thought marcel had tidied the perl thing to auto-sense 18:38:28 but fwiw, I use a general purpose environment that I've changed very very rarely 18:38:53 my last change was 18 months ago, before that it was 26 months ago 18:38:59 so if it's breaking _often_ I have no idea what you could be doing 18:39:38 well part of it was the VM runs bloody 18:39:43 so do I 18:40:01 so if you don't update it and then run onu, it first pulls in all the updates 18:41:17 otherwise I have an env files for various options that have the right flags for everything so I know what I should expect 18:41:51 but since it's based on the default env files 18:42:18 and also so I don't have to worry about 'well you did a bunch of stuff to your env file that was wrong....' 18:43:15 a useful trick there is just to source the normal one, and then override bits. 18:43:16 but those also unfortunately hard code the perl and python versions and java (though for python, I think it ignore the micro, so that's been less of an issue) 18:43:22 if anyone is following along and newer to this than jbk 18:43:23 Regardless of anything else, I finally migrated pretty much all of my .env files to auto-sense things like that 18:43:25 export PERL_VERSION=5.`perl -MConfig -e 'print $Config{PERL_VERSION}'` 18:43:32 well i made the stupid mistake of actually reading the env files 18:43:39 and modifying the values where it says 'modify these' 18:43:50 when in fact they then get overwritten 1000 lines later in the file 18:43:54 and get surprised 18:44:10 because my changes are lost... 18:44:12 Fair - https://downloads.omnios.org/env/build-gate-on-bloody.env is better. 18:44:21 which you find out an hour+ later 18:44:37 nahamu: I got a core with a conceptually hung tailscaled, but there are no smoking guns and no real idea what's up. all I can say is we're waiting to read the tun device and otherwise sleeping 18:44:43 (which is a bit annoying when you've only got a few hours to work on something and you've just lost over half of it fighting the build env) 18:44:47 nahamu: but with green threads I'm not even sure if that much from the core is actually logically true 18:45:12 (it wedged up between the first line i typed to jbk today and the second) 19:00:01 FYI: for CMake fans, I have filed https://gitlab.kitware.com/cmake/cmake/-/issues/26302 20:04:52 oh, that's going to break a lot of software 20:15:37 so I missed what that's in reference to jperkin 20:15:38 cmake? 20:16:21 yes, specifically widespread usage of 'if(CMAKE_SYSTEM_NAME MATCHES "SunOS")' 20:17:39 ah, yeah, that's rough 20:17:52 and also why an autoconf triple is a terrifying proposition 20:18:15 for right now, aarch64-unknown-solaris2.11 even 20:18:23 because `*-*-solaris2.*)` 20:51:58 jperkin: I think we have to do it though 20:57:02 I would love an IPD (on which I would try to collaborate) 20:57:12 perhaps of even wider scope 20:57:20 now that one of the larger problems we've had in the past has been solved 20:57:29 it's possible we could actually like, talk about the problem and what the solutions are 20:57:33 lol 20:57:45 Indeed 20:58:40 it would - in this context - probably also make sense to teach clang about illumos 20:59:52 I concur! 21:51:47 [illumos-gate] 16748 asy: support higher baud rates -- Hans Rosenfeld