Kris Kennaway wrote:
> How does one fix this in a library? I've been moving the
> initialization to main() for applications.
Use assembly glue to put it in a linker set that gets pulled
in by the .init code.
This will only work for user space code, since it depends in
the crt0 treating it like a C++ binary (linker sets are a C++
feature which FreeBSD uses all over anyway).
I'm not totally convinced this is really the way to fix this,
since I'm not totally convinced that this isn't an introduced
problem, rather than a real problem (e.g. perhaps the stdio
changes were not completely and totally well thought out, if
how to handle this problem wasn't part of the changes).
If it's now a requirement, it's very tempting to put the code
in the entry code, before it even calls "main" (e.g. in crt0
proper, rather than in a linker set crt0 knows about).
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message