Hmmm. The origional plan had said /lib.
yeah, i know. that's why i told you :-) basically, enough people
complained that not using /libexec/ld.elf_so would be to break the
consistency of the system, yadda yadda yadda. i don't care and
prolly would have preferred to not have a new /libexec for one file,
but whatever ...
NetBSD is native libc. FreeBSD is GNU libc. Beward of trying to run native
applications, however; they may or may not be linked against the same
versions of various libraries that Debian has (though, in theory, if the
soname matches it SHOULD work, and if it doesn't, it should fail on the
inability to link at runtime).
i'm not so worried about non-libc shared libraries, but libc itself.
how do i take an application build for a normal freebsd host and run
it on debian/freebsd? is their libc around somewhere for it to find
or will it try to use glibc (and almost definately fail)?