Re: libthread and libtrivfs

[Neal H Walfield]

Stubs are provided for libthreads.  The stubs (which are linked in if
an explicit request to link against libthreads is not added) should be
used for single threaded applications using multithreaded libraries
(such as libtrivfs).  Multithreaded applications cannot safely use the
stubs; they obviously need real locking.

libports is different.  There are no useful stubs that we can provide.
I.e. there is nothing worth optimizing which contrasts the previous
case.  Again, a single threaded application indirectly using
libthreads can safely elide locking by faking it, etc.

You do not need to add `-lports' to the link line as a DT_NEEDED
dependency (look at `obj-dump -p /lib/libtrivfs.so') is declared when
the libtrivfs share object file is created.