On Fri, Jan 13, 2012 at 4:18 PM, Kostik Belousov <kostikbel_at_gmail.com> wrote: > On Fri, Jan 13, 2012 at 04:11:22PM +0200, Andriy Gapon wrote: >> on 13/01/2012 14:57 George Kontostanos said the following: >> > Still the question remains regarding COMPAT_FREEBSD8 and how does this >> > affects ports/misc/compat8x/ >> >> Looks like all the previous hints have not been clear enough. >> There is no direct relation between COMPAT_FREEBSD8 and misc/compat8x. >> COMPAT_FREEBSD<X> options are only needed when going from release X to release X+1 >> there was a change to an existing system call at the kernel-userland boundary. >> A side note: kernel options affect only what's in the kernel, quite obviously. >> misc/compat<X>x contains versions of shared libraries from release X that are no >> longer present in X+1. > > Additional twist is that not every change at the kernel/usermode boundary > is covered with backward-compatibility shims. Recent example is the CAM > ABI change, which makes libcam.so.5 from the compat8x useless. Thanks to all for your input. It looks quite obvious to me know and I think this clears any further confusion. Best Regards, GeorgeReceived on Fri Jan 13 2012 - 14:13:32 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:23 UTC