Re: Bug#649038: elfutils FTBFS on kfreebsd
On Mon, Nov 11, 2013 at 03:32:09PM +0100, Mark Wielaard wrote:
> > >> - The other failures look like issues with the /proc interface
> > >> on the install. Does the /proc interface follow the Linux kernel
> > >> /proc interface that some of the tests rely on?
> >
> > Yes. But as there's no standard covering Linux-style /proc, it can't
> > ever be 100% complete. FreeBSD developers provide an emulated
> > "linprocfs" for compatibility purposes and try to keep up, but depending
> > on what you do it might not work.
> >
> > Also, this is only provided on GNU/kFreeBSD. FreeBSD systems either use
> > the native FreeBSD-style /proc or none at all. If you want to support
> > FreeBSD as well, it's better if you use sysctls or whatever you need for
> > what you're testing.
>
> This is mainly for the libdwl dwfl_linux_* group of
> functions. /proc/PID/maps, /proc/PID/exe, /proc/PID/mem, /proc/TID/status and /proc/PID/auvx are used to inspect user space binaries with libdwfl. And /proc/kallsyms and /proc/modules are used to inspect kernel modules with libdwfl. See libdwfl/linux-proc-maps.c (backend for dwfl_linux_proc_report) and libdwfl/linux-kernel-modules.c (backend for dwfl_linux_kernel_report_kernel and dwfl_linux_kernel_report_modules). Someone might want to provide backends for kfreebsd if the corresponding libdwfl dwfl_linux_* functionality is wanted there. The kernel parts probably won't easily work, the user space parts probably will assuming the /proc interface is linprocfs style and sufficiently compatible.
My understanding is that the part from /proc that we need for user
space works, except in a chroot where the path that is mentioned
is not relative to the chroot.
Kurt
Reply to: