bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libposix stuff


From: Bruce Korb
Subject: Re: libposix stuff
Date: Mon, 08 Nov 2010 14:09:47 -0800
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100914 SUSE/3.0.8 Thunderbird/3.0.8

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.  If it is only OS X,
then I would think that this would work:

char * program_name;
#ifdef OSX //whatever
#pragma weak program_invocation_name // program_name not being program_name.
#endif

requiring a call to set_program_name just seems so wrong for a posix lib.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]