Re: libposix stuff

2010-11-22 Thread Bastien ROUCARIES
Dear bruce, Have you tested the previous program ? Bastien On Mon, Nov 15, 2010 at 12:41 PM, Bastien ROUCARIES wrote: > Le mardi 9 novembre 2010 13:31:03, Bastien ROUCARIES a écrit : > Bruce could you try the following program under HPUX ? It will print the > program name (i put the following

Re: libposix stuff

2010-11-15 Thread Bastien ROUCARIES
Le mardi 9 novembre 2010 13:31:03, Bastien ROUCARIES a écrit : Bruce could you try the following program under HPUX ? It will print the program name (i put the following code in public domain if copyrightable I do not think it is) Bastien #include #include #include int main() { stru

Re: libposix stuff

2010-11-09 Thread Bastien ROUCARIES
Le lundi 8 novembre 2010 23:09:47, Bruce Korb a écrit : > 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

Re: libposix stuff

2010-11-08 Thread Thien-Thi Nguyen
() Bruce Korb () Mon, 08 Nov 2010 15:01:18 -0800 OK, I'll throw together a little script that looks at the dependencies of every POSIX module. It just so happens the latest make-html also computes fanout, albeit without any classification. Since last posting, it has been modified to mine

Re: libposix stuff

2010-11-08 Thread Bruce Korb
On 11/08/10 14:50, Eric Blake wrote: > 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 pr

Re: libposix stuff

2010-11-08 Thread 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 g

Re: libposix stuff

2010-11-08 Thread Bruce Korb
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), whic

Re: libposix stuff

2010-11-08 Thread Ralf Wildenhues
Hello, * Bruce Korb wrote on Mon, Nov 08, 2010 at 05:29:57PM CET: > On 11/07/10 12:40, Bruno Haible wrote: > >> -extern char *program_name; > >> +char *program_name; > >> ... > >> + char const *p = program_name ? program_name : "unknown"; > > > > No, this is not OK, for two reasons: > > 1)

Re: libposix stuff

2010-11-08 Thread Gary V. Vaughan
Hi Bruce, Bruno, On 8 Nov 2010, at 23:29, Bruce Korb wrote: >>> $ ls -1 $(allbut usr/local/include/*.h - $( >> egrep -l '#ifndef _LIBPOSIX_' usr/local/include/*.h) ) usr/local/include/arg-nonnull.h usr/local/include/iconv_open-aix.h usr/local/include/iconv_open-hpux.h usr/l

Re: libposix stuff

2010-11-08 Thread Bruce Korb
On 11/07/10 12:40, Bruno Haible wrote: >> /* The calling program should define program_name and set it to the >> name of the executing program. */ >> -extern char *program_name; >> +char *program_name; >> ... >> + char const *p = program_name ? program_name : "unknown"; > > No, this is