>> Then I think possibly the right answer for the moment is for me to
>> excise rump from my tree entirely. [...]
> But it seems really obvious that you should fix the rump build and
> write some atf test cases for your SCM_MEMORY stuff, and then you
> will be able to test it automatically.
I
Mouse writes:
>> The rump build is done with separate reachover makefiles. [...]
>
> Hm. Then I think possibly the right answer for the moment is for me to
> excise rump from my tree entirely. I can't recall ever wanting its
> functionality, and trying to figure out what the dependency graph
Date:Sun, 12 Jan 2020 22:36:23 -0500 (EST)
From:Mouse
Message-ID: <202001130336.waa17...@stone.rodents-montreal.org>
| I can't recall ever wanting its functionality,
It is used mostly by a lot of the ATF tests.
| and trying to figure out what the dependency
>> But now, when I try to build the world, rump_nfs fails to link,
>> citing as undefined two routines I added to uipc_usrreq.c which are
>> referred to from uipc_syscalls.c.
>> This leads me to ask [...] where can I get the dependency graph
> The rump build is done with separate reachover
> Date: Sun, 12 Jan 2020 21:56:30 -0500 (EST)
> From: Mouse
>
> But now, when I try to build the world, rump_nfs fails to link, citing
> as undefined two routines I added to uipc_usrreq.c which are referred
> to from uipc_syscalls.c.
>
> This leads me to ask - and I realize it's possible nobody
I've just got something new working (a way, sibling to SCM_RIGHTS, for
passing memory space between processes). I've been doing this in 5.2,
because that's what I have handy.
But now, when I try to build the world, rump_nfs fails to link, citing
as undefined two routines I added to uipc_usrreq.c
