Re: Problem with sys_select on Cygwin

2016-03-29 Thread Paul Eggert
Ken Brown wrote: Yes, I thought of that too. Someone would have to look at each of them and decide if they apply to newlib in general. I would be willing to take a shot at this. But I would do it as I have time, not necessarily all at once. Would you rather wait until I've finished this and t

Re: Problem with sys_select on Cygwin

2016-03-29 Thread Ken Brown
On 3/29/2016 9:10 PM, Paul Eggert wrote: On 03/29/2016 07:00 AM, Ken Brown wrote: - name" problems on Cygwin. + name" problems on newlib systems.. No double '..'; and maybe the comment could say "newlib systems, including Cygwin", since that is our most common newlib system. Otherwise, I'

Re: Problem with sys_select on Cygwin

2016-03-29 Thread Paul Eggert
On 03/29/2016 07:00 AM, Ken Brown wrote: - name" problems on Cygwin. + name" problems on newlib systems.. No double '..'; and maybe the comment could say "newlib systems, including Cygwin", since that is our most common newlib system. Otherwise, I'm okay with the change. Could someone in

Re: Problem with sys_select on Cygwin

2016-03-29 Thread Ken Brown
On 3/21/2016 6:47 PM, Eric Blake wrote: On 03/21/2016 03:43 PM, Ken Brown wrote: On 3/21/2016 1:32 PM, Paul Eggert wrote: Eric Blake wrote: This feels a bit too broad - it assumes that everyone is compiling with ONLY the latest newlib headers; remember, the cygwin header changes have NOT been

[PATCH 4/4] main.mk: remove sc_program_name

2016-03-29 Thread Pino Toscano
There is no more need to use set_program_name in tools (getprogname is enough for most of the cases). * cfg.mk (local-checks-to-skip): Remove sc_program_name. * top/maint.mk (sc_program_name): Remove. --- ChangeLog| 6 ++ cfg.mk | 1 - top/maint.mk | 9 - 3 files changed, 6 i

[PATCH 0/4] New getprogname module

2016-03-29 Thread Pino Toscano
Hi, as discussed in [1], this series adds a new getprogname module. All it does is providing a getprogname function, much like what is found on e.g. *BSD systems, and using it in gnulib instead of progname. Also, using it explicitly by modules avoids gnulib users the need of either use the prognam

[PATCH 1/4] getprogname: new module

2016-03-29 Thread Pino Toscano
This provides a LGPL module for getting the name of the current program, using the same API found on *BSD systems. * lib/getprogname.c, lib/getprogname.h, m4/getprogname.m4: * modules/getprogname: New files. --- ChangeLog | 8 lib/getprogname.c | 45 ++

[PATCH 2/4] Port modules to use getprogname explicitly

2016-03-29 Thread Pino Toscano
... instead of requiring progname to be used (or program_name to be provided). * lib/argmatch.c: Do not include progname.h. [TEST] (program_name): Do not define. [TEST] (main): Call getprogname instead of using program_name. * lib/c-stack.c: Do not include progname.h. (program_name): Do not define.

[PATCH 3/4] Port tests away from progname

2016-03-29 Thread Pino Toscano
Modules which need the program name are using getprogname. * modules/acl-tests (Depends-on): Remove progname. * modules/argmatch (Depends-on): Likewise. * modules/argmatch-tests (Depends-on): Likewise. * modules/argp-tests (Depends-on): Likewise. * modules/argp-version-etc-tests (Depends-on): Like

ping [PATCH] early check for PowerPC AIX object mode

2016-03-29 Thread Michael Haubenwallner
any comments at least? Thanks! /haubi/ On 03/17/2016 03:34 PM, Michael Haubenwallner wrote: > Native PowerPC AIX tools do accept only 32 bit objects by default. > They either need the -X32_64 commandline flag to accept both, or the > OBJECT_MODE=64 environment variable to switch to accepting 64 bi