06:30:49 If I set the IPv6 "forwarding" property to off 06:31:04 Why does the computer still forward IPv6 packets from interface to interface? 06:31:51 If I turn the IPv4 forwarding property off, it immediately stops forwarding things 06:43:52 bug? 06:52:18 does that target interface have forwarding enabled? ire_recv_forward_v6() is checking ill_flags & ILLF_ROUTER on source and destination 06:55:31 ipadm show-ifprop -p forwarding 08:58:21 Yeah, it's on for the interfaces 08:58:32 I guess there's a bug with the global toggle then 09:03:42 I have filed illumos#18171 09:03:48 ... fenix? 18171 09:04:34 I don't know what it is about this bot but I seem clinically incapable of triggering it 09:04:41 fenix? illumos 18171 09:04:42 BUG 18171: IPv6 "forwarding" property does not inhibit forwarding (New) 09:04:42 ↳ https://www.illumos.org/issues/18171 18:50:14 [illumos-gate] 18101 bhyve: use speed in hci to allow backend modify it. -- ShengYi Hung 20:42:46 danmcd: I have never used the auto-test thing where it derives the tests from the directory 20:43:03 danmcd: aside from your experience today, does it tend to be fine? 20:44:34 I have almost 4 years of test results to make me feel pretty happy about all of that. 20:45:21 I run the tests using this: https://github.com/TritonDataCenter/illumos-joyent/blob/master/usr/src/test/smartos-test/smartos-test.sh 20:45:44 Good part is here: https://github.com/TritonDataCenter/illumos-joyent/blob/master/usr/src/test/smartos-test/smartos-test.sh#L350 20:47:29 that might help me clean up this arm64-gate wad some 20:47:45 just say "run the ../32 and ../64 tests", rather than enumerating them all twice 20:47:55 (and make the ../32 ones i86pc-specific) 20:51:39 [illumos-gate] 18161 dmake(1) could use posix_spawn() to run commands -- Andy Fiddaman 20:52:48 andyf: glad that circumstances got that one into my merge :) 20:53:30 It's time to run another another build on aarch64! 21:07:04 andyf: if you want to measure yourself, you'll want a baseline with only michael's fixes 21:09:38 I can do that. dmake is self-contained so copying the binary back and forth gives a clean way to test. 21:12:43 andyf: looks like the optimized descriptor-copying thing for the spawn syscall turned out to be not too hairy to pull off. Nice! 21:19:13 Yes! Thanks for suggesting that, I'm not sure I'd have thought to do it otherwise. 21:19:30 richlowe / andyf: so I attempted to use the configure command in the README.md in https://github.com/illumos/gcc and the subsequent build failed in one of the later stages (with a ".. already configured" error, I think.. it's been a while). 21:19:39 I think I'm missing a secret handshake.. 21:21:44 (want to clear up the open issues on my pull request that improves locale support in libstdc++) 21:21:48 I've only ever used the omnios build scripts to drive that (https://github.com/omniosorg/omnios-build/blob/master/build/gcc14/build.sh#L98 ) but I should take a look at the README 21:22:34 I was confused by the "../../configure ..." instead of "./configure ..." 21:22:48 not sure what that was supposed to imply.. 21:23:18 Probably an out of tree build thing, with that being the path back? I will read and stop guessing. 21:24:42 if I wrote it, it will assume an out-of-tree build 21:24:45 sorry 21:25:38 "../../configure" reads to me as two-subdirs-deep-in-tree (which ones?) rather than out-of-tree.... 21:27:06 probably gcc/build/foo/ 21:53:57 sommerfeld: almost certaily gcc/build/, indeed 21:58:27 if people are looking at illumos/gcc, can someone bump the default branch? :) 21:58:30 (if they didn't already) 22:42:32 heh yeah 22:42:35 that got me the other day 23:32:04 richlowe: I'd change it (illumos/gcc default branch) if I had access but I don't think I do..