00:02:41 Thats step one I guess. I eventuelly also need to get things into the illumos buildsystem and not hayashis 00:03:11 but modifying hayashis system first is a good idea 15:46:59 I am having trouble with ipv6 again, at least it's not a kernel panic this time :) 16:28:32 I can't recall the IPv6 panic... did we fix it (if so, cool, if not do you have a vmdump.N file you can share?)? 16:29:44 As for now, what's happening? (Pardon latency & jitter 'cause it's a release-week-Wed at month's beginning so it's a chock-full-of-meetings day). 16:31:12 oh, the ipv6 panic was fixed within the day and I almost learned the kernel debugger in the process but it's been months so I've mostly forgotten :) 16:45:19 I can't get ping to work to an ipv6 address and it looks like my routing table is the problem 16:45:27 wgetpoaste 16:45:31 oops] 16:49:58 http://sprunge.us/x2NwD2 16:51:26 ifconfig -a 16:51:30 sigh] 16:52:48 http://sprunge.us/NdSJrU 16:53:10 rge0:3 has my currently valid ipv6 addr 16:54:27 I'm betting it will work if i reboot and don't have yesterday's addresses still in the kernel 17:11:44 rge0:3 has a different /64 prefix so it should work, but I can imagine source-address selection takes it rge0:2 first. 17:11:46 Try this: 17:11:50 ifconfig rge0:2 down 17:11:59 That'll take that IPv6 offline. 17:12:38 It'll save you a reboot until next reboot. 17:13:11 If you snoop rge0 for IPv6 pings, you can confirm a bad source address selection on those default-route pings (if you haven't already down-ed rge0:2). 18:06:23 [illumos-gate] 14928 pcieadm rc event collector association decoding -- Robert Mustacchi 18:07:58 thanks, I had already started a reboot and that fixed it :) next time I know to try taking the extra interface down first though, tyvm 18:09:34 it looks like this could turn into an ongoing problem since my ipv6 changes on a near daily basis when i get a new ipv4 18:09:47 i might have to write a script 18:27:44 I do build Illumos on that machine but I also serve some personal web content there for clients to look at. 18:28:48 So, I'm actually working on getting both of my domains to show up on my dyndns provider with both ipv4 and ipv6 addresses 19:55:38 [illumos-gate] 14951 fix ::sysregs under mdb-bhyve on AMD -- Patrick Mooney 22:14:51 [illumos-gate] 14901 remove remaining a.out support from sgs -- Richard Lowe 22:58:39 Ok, now I have a gnu Makefile question. Does anybody know if... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/6ddddbadd3e5607df27f2cb379d09af66851e7f3) 22:58:49 modulo missing endif ofcourse 22:59:17 checkmake says yes gnu make says `make: Fatal error in reader: ../Makefile.master, line 38: Unexpected end of line seen` 23:08:36 I believe you just have 'ifeq' and have to check it against an empty string 23:09:52 but I don't know why I think that, what you want to do works for me 23:10:43 https://gist.github.com/richlowe/54c1f66fbf9aae8a4186db1add5184c4 23:12:00 I don't know what you're doing -- or why you're doing it -- but if this is for ARM, it's almost certainly easier to port our make to your host machine than to port our build, properly, to gmake. 23:12:16 I know andyjs and some other people had some magic that ports our build improperly to gmake, too, which might help you in the very short term 23:12:54 but I believe joerg took sun make and did... joerg things to it, which should get you a long way. 23:26:58 richlowe: it's arm. So the situation right now is Hyashi has ported our whole build to gmake. And I want to build ontop of OI. I got our cross toolchain compiled and want to use that to compile Hyashis build system. It is rebased on latest illumos-gate as of 4 days ago but all gmake. 23:28:05 I figured I could get away by switching some paths to host tools which linux needs to compile and then use OI to build the existing build. but for whatever reason gmake on OI does not like that line. 23:48:14 richlowe: i think somehow make is being invoked but I haven't found out how, there is a variable $(MAKE) but that shows gmake in the line before... 23:56:12 ah found where make gets called 23:57:16 it's a hardcoded make in the same file as $(MAKE), well that solves the problem :) 23:58:56 now it's happy :)