On 16.11.2013 11:06, Alexander Nasonov wrote:
+./usr/lib/librumpkern_sljit.so base-rump-shlib rump
+./usr/lib/librumpkern_sljit.so.0 base-rump-shlib rump
+./usr/lib/librumpkern_sljit.so.0.0 base-rump-shlib rump
A similar change was sitting in my local tree for quite a while but
sljit API isn't yet stable enough to wrap it into a DSO.
I kept bpbfjit and libsljit private (LIBISPRIVATE=yes) and used them
only for libsljit and libbpfjit tests.
Is it possible to do something similar in rump framework?
There is no rump kernel ABI in the normal lib.so.1.2.3 sense. The
public ABIs (e.g. syscall) are stable, but any in-kernel ABIs are
subject to the same rules as for kernel modules. Technically, it would
be more correct to install rump kernel components into something like
/usr/lib/x.yy.z (cf. /stand/modules), but so far it hasn't been an issue.
So, in my opinion, there is no need to excessively worry about compat in
librumpfoo_sl/bpfjit, unless you explicitly want to expose an ABI from
there to userspace processes.
