Re: V3 testsuite results (with required minor patch), FreeBSD 3.4

[Loren James Rittle <rittle at latour dot rsch dot comm dot mot dot com>]

After getting --enable-cstdio=libio to build, I wrote this in private mail:

> *Every* shared build is failing with (at least) this set of errors:

> [...]/libstdc++.so: undefined reference to `_IO_funlockfile'
> [...]/libstdc++.so: undefined reference to `_IO_flockfile'
> [...]/libstdc++.so: undefined reference to `_IO_cleanup_region_end'
> [...]/libstdc++.so: undefined reference to `_IO_lock_fini'
> [...]/libstdc++.so: undefined reference to `_IO_lock_unlock'
> [...]/libstdc++.so: undefined reference to `_IO_lock_init'
> [...]/libstdc++.so: undefined reference to `_IO_cleanup_region_start'
> [...]/libstdc++.so: undefined reference to `_IO_lock_lock'
[...]
> Any clues?

It appears that I need to provide all these functions if I want to
configure --enable-cstdio=libio --enable-threads\=posix for a given
port that has no native libio.  Is that correct?

Is there a formal specification of the semantics required of those 8
functions?

I think I see how to directly map _IO_lock_* to the POSIX thread
interface after studying bits/stdio-lock.h.  It seems wrong that
this should have to be encoded in config/os/XXX/bits/os_defines.h,
but that is where I intend to land it until we decide otherwise.

Regards,
Loren