[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: symbols in libc_r not in libc
From:       Terry Lambert <tlambert () primenet ! com>
Date:       1998-02-27 21:37:41
[Download RAW message or body]

> As far as I can understand weak symbols, you can add your own version of
> __error() in Xlib, as a weak symbol.  That way, the programs that do not
> use libc_r get the __error() from Xlib, and the ones that do from libc_r
> (I take it that the libc_r __error() is a strong symbol).  This should 
> give you exactly what you need exactly where you need it.
> 
> The Xlib implementation of __error() should naturally just return the
> address of errno.  Don't forget to undefine errno when you implement
> the Xlib __error().
> 
> Hope I didn't miss anything.

How about "FreeBSD headers should not be variant based on the
manifest constant 'THREAD_SAFE'"?

The libc is the correct place to put libc_r compatabilities...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message

[prev in list] [next in list] [prev in thread] [next in thread]