Re: FreeBSD port (36): config support

[Roland McGrath <roland at redhat dot com>]

> I wanted to avoid clashing with FreeBSD's BSD libc, which is currently
> called libc.so.4 and (as I understand it) might be called libc.so.5 in
> FreeBSD 5.0.
> 
> If the soname really is irrelevant, I'll use libc.so.1. That will
> avoid clashing with FreeBSD 5.0 libc as well :-)

You get to say what is relevant for your port.  If libc.so.5 might be used
by FreeBSD soon, then I would think libc.so.6 would follow eventually.
You have to decide whether you want to care about the FreeBSD sonames or not.
I don't really know what the goals of your system are.  Probably you just
want to ignore the soname clash issue since you are not providing an
ABI-compatible libc at any rate, and support FreeBSD-compatible soname
libraries (if you want that) by having either the PT_INTERP value (i.e.
the file name of the dynamic linker), or some magic the dynamic linker
can detect, indicate disjoint library search paths.

> The oldest_abi setting that I have in
> sysdeps/unix/bsd/bsd4.4/freebsd/configure.in appears to have the same
> effect:

Yeah, maybe.  But the preferred way to do it is in shlib-versions,
and that is definitely clearer and more sure to continue working the same.