00:05:42 i'll try adding that to the makefile (LD_DEBUG=libs ... i always forget about that) and see if that helps 04:12:31 out of curiousity, has anyone messed with building illumos-gate with libressl instead of openssl 05:51:29 elwisp: ping, do you use oxide computer? in the chat log, I read the message that you are using helios, it is oxide’s os for oxide cloud computer, I’m interesting the default raid for the pool, would you please show me the ‘zpool list -v’ for the node? a big thanks 06:10:49 tozhu: its just Helios in a VM that i am testing 06:13:17 tozhu: ill sent it to you in PM 06:13:37 jclulow it will cause recursive mutex panic 09:55:16 jbk I am pretty sure that racktop do - illumoe 13909 (fenix) 09:55:25 illumos 13909 fenix 09:55:26 BUG 13909: Want support for building against LibreSSL 3.X (In Progress) 09:55:26 ↳ https://www.illumos.org/issues/13909 | https://code.illumos.org/c/illumos-gate/+/1581 14:21:49 andyf: actually all of that was torn out because of recent openssl changes 14:21:59 (which is incredibly disappointing) 14:29:10 Out of gate? I missed that happening. 14:29:17 (if so) 14:56:53 whatever is there apparently has issues with the latest bits in ways that weren't explained 15:12:36 tsoome: i know i've asked this before, but before i forget, is there any sort of upstream for efiapi.h ? I have a branch with a bunch of newer EFI GUIDs (mostly just so you can easily identify what protocols are present on a system) 15:12:53 which I added by hand, but if there's a better source, I'd like to use that 15:13:05 (https://github.com/illumos/illumos-gate/compare/master...jasonbking:illumos-gate:efi-guids if you want to see) 15:27:42 rmustacc: a while back we had talked about how to represent an internal M.2 slot for an NVMe drive in fmd/fmtopo... would the changes you recently integrated include bits to better express that? 15:28:18 (my recollection is that you thought you had some stuff you were working that'd help... wondering if this was it) 15:29:45 jbk - I have done work to add support for openssl 1.1, and then for 3.0 but I have never removed any libressl guards or related. When I did the work for 1.1 I regression tested with 0.98, 1.0 and 1.1, but not libre so I expect that patch in 13909 is still needed. If anything was torn out I am not aware of it. 15:30:23 andyf: i meant in our stuff in our build, not upstream... 15:30:45 Ah, ok, that's a relief. 15:30:50 sorry for the confusion 15:31:02 still trying to wake up after a marathon day yesterday 15:31:08 ($@#$#@$@# perl) 15:52:59 jbk: I certainly have a better idea of how I would represent the M.2s and can point you to how we did for our system, with caveats. 15:53:26 that'd work 15:54:04 The biggest set of caveats is that we're trying to not put everyhting in hc and are creating different trees for that. 15:54:19 So hc strictly represents mechanical releationships, devices in slots, bays, sockets, etc. 15:54:51 However, we've also separately added things like the a pcie tree and more to try to have something that is representable (not just on our system, but more generally). 15:54:59 I can shoot you an e-mail with more details? 15:55:22 yeah that's fine 15:55:35 i'm kinda hobbled right now because my comcast has been down since late last night 15:55:41 so my laptop is tethered to my phone for work 15:55:53 but means i have to disconnect to reach my home network :) 15:56:03 so it'll be later before I can dig in 15:56:13 (my goal is i want to represent the stuff in my home server) 15:57:08 My ISP sent me an email today saying if I want to keep my static IP, I need to click on a link in the email to let them know. Clicking on the link immediately changed my IP address at the ISP side, apparently so I'm still recovering. 15:57:15 I /do/ have IPv6 now though, so that's something 15:57:52 i have the front drive bays and USB ports where they're identified now with what you'd see on any product documentation or physical labels on the system 15:58:10 but the network ports and the M.2 slot were the last bits 16:00:26 about 2 months ago, my internet down for like 10-12 days 16:00:35 it'd come back for like 45 mins, then die for hours 16:01:29 I just re-discovered fire using the incremental file in nightly, my a8 take like 5 hours to build-gate now just 2 using incremental 16:27:38 andyf: welcome to the new world with more odd network quirks now that you have IPv6 16:27:59 once things settle 16:28:11 i should dig up some issues 😅 16:28:39 Well, I live in a mostly IPv6 world at work, so about time I caught up at home :) 16:33:37 andyf we need an additional reviewer for the mdb vmm change so dan could approve it for RTI, I don't know who else could take a look 16:36:13 neirac - it looks like Jordan added herself as reviewer a while back, I can ask her if she still intends to review. 16:43:57 andyf thanks a lot. 16:46:28 I have one question regarding this doc https://illumos.org/docs/contributing/gerrit/ in section 2, to copy the hooks I always need to add -O flag to scp if I don't do it it does not work, I'm in omnios. Someone else had that problem? 18:04:30 you copy that once... well, unless you have multiple repositories 18:14:26 tsoome oh, yes but when I first setup this on a new machine and copy the hooks scp does not work without the -O flag, is that flag required? 18:15:33 what does -O do? man scp does not seem to mention it.... 18:16:26 ah, other system does... Forcing the use of the SCP protocol may be necessary for servers that do not implement SFTP 18:16:55 so it depends on server 18:18:27 yes, for me the -O flag works on code.illumos.org 18:19:06 should be just scp according to the documentation 18:19:36 or my install is the problem, just asking if someone else needs to use -O 18:25:23 is not bad, just that I forgot about it as I only needed once, but when setting up other machine I bump into it. 20:19:24 Is it required to do a non-debug build to create a onu?, or I just could skip the non-debug build? 20:20:23 depending on change, you may want to test both (thats the onu is for) 20:20:51 But strictly speaking, multi-proto is never required to use onu. 20:21:01 You either pass in debug or non-debug packages. 20:21:27 During early development, for example, I will pretty much only ever build and use debug until the end. Some people are the opposite. 20:22:02 rmustacc , tsoome_ thanks, I was building debug and non-debug for a change and taking a lot, I'll work with debug only then. 20:22:50 Depending on what you're doing, I also find it helpful to just use dmake install in the single package I'm working on and then rebuild packages. 20:23:01 *single directory 20:23:47 rmustacc oh yes, on changes on mdb I do that, I was finishing adding a tcp socket option so I assume needed to do a build 20:24:11 It's always safer. 22:05:57 out of curiousity, any thought given to the 'next' version of gcc to target for building? 22:09:00 you mean, for gate build? 22:09:05 yeah 22:09:07 13 22:10:52 IIUC, 13 actually support plugins -- I wonder how interesting it'd be to do our changes (e.g. -msave-args) as plugins 22:11:19 There's a PR up on github/illumos/gcc that I need to get back to. It's just carrying forward the patches though at this point. 22:11:25 I have some 22 or so cleanup patches still in queue with gcc 12, 13 will add about 10 more, with *current* warning blockers 22:11:33 but omnios has gcc13 and userland is built with it these days 22:13:03 13 because of C23 22:13:34 well, it will enable us to walk that path;) 22:19:33 anyhow, time to get some sleep... 22:21:00 just saw the first round of patches to clean up gcc 14 warnings in various open source projects go by - apparently -Walloc-size in gcc 14 pays attention to the order of calloc args 22:21:31 i have a change that cleans up most of the warnings in mac... there's a small number i'm unsure of, so those are in a separate commit, but I should probably get those up once I've had a chance to run them through some smoke tests (aside from some missing cases in a few switch statements, mostly just assigning default values) 22:22:51 https://gitlab.freedesktop.org/search?scope=merge_requests&search=-Walloc-size 22:23:33 smatch does that too, but I be suppress that in some places at least. 22:23:41 *I bet we 22:27:36 https://github.com/jasonbking/illumos-gate/commit/a83768958079961f4f22348601f0fe15eee92e3e for the curious 22:49:57 is there like a rosetta stone to compare our tcp struct field names vs the one in Linux?, I thought of trying to search comments in the lx brand commits 22:50:20 I wouldn't expect there to be. 22:51:43 Is there something you're trying to figure out how to implement? 22:53:46 rmustacc yes, I'm missing to map the values from tcp_info, I'm implementing TCP_INFO socket option I'm missing just returning the right values, here https://smartos.org/bugview/OS-4525 is the tcp_info struct but the names don't match or I'm missing to find the ones needed in tcp_t 22:53:47 → OS-4525: lxbrand implement getsockopt(TCP_INFO) (Open) 22:54:10 right now I'm just returning made up values, but not ideal 22:56:54 I see. That's not going to be a straightforward question to answer. 22:56:59 There's a lot of research required. 22:58:06 rmustacc yes, I was reading how are those calculated, and maybe some fields need to be added to get the information, I'll staart with just the fields that some applications require 22:59:35 Are there applications outside of lx that are looking for it? 23:01:41 rmustacc not yet 23:12:47 rmustacc I'll try to read a little more about the fields in other platforms and how they map those values.