Source-Changes archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: basesrc
> Modified Files:
> basesrc/lib/libc/gen: errno.c
>
> Log Message:
> Back out previous: when statically linking executables a warning will be
> displayed for the reference through __errno(), which is really wrong.
Why not just do it if compiling PIC code? (i.e. so the warning will
end up in a shlib but not in the .a.) Will that have the right
effect?
you'll still end up with warnings from the ld.*so programs, because
they link with libc_pic.a, but that's not so bad.
do __warn_references() have to be in the same file that defines the
symbol? maybe a special object file containing only warnings like
this, that gets included in the shared library...
cgd
--
Chris Demetriou - cgd%netbsd.org@localhost -
http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.
Home |
Main Index |
Thread Index |
Old Index