Re: libposix stuff

[Eric Blake]

On 11/08/2010 03:09 PM, Bruce Korb wrote:
> On 11/08/10 13:29, Ralf Wildenhues wrote:
>>> [...] "a.out" format:
>>>     char *program_name;
>>> this on a line by itself was both a declaration and a definition.
> 
>> On OS X that may just be the case because libtool forces -fno-common
>> (for some good reason, but I tend to forget what it was), which disables
>> common sections.
> 
> I didn't think my memory was getting that bad.....
> 
> Then what is the solution?  It would not feel right to require programs
> that are asking for "libposix" to also call a non-posix function just
> because it is convenient for the error POSIX module.

error() is not POSIX.  Maybe the thing to do is figure out what in
libposix is dragging in error(), and work on breaking that dependency.
That way, a package using libposix then makes their own decision of
whether to supplement things with error() and program_name.

-- 
Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

signature.asc
Description: OpenPGP digital signature