'static' in array-size func parm

I recently learned that GCC 3.4.3 on Solaris 10 cannot compile: int last (int count, int all[static count]) { return all[count - 1]; } (valid C99, AFAIU), and have changed GNU RCS to work around the situation, in the form of a configure-time test[0], a simple cpp macro[1], and then variou

Re: Missing symbols when compiling gettext on OSX 10.8

Paul Eggert writes: > Thanks for reporting this. Since your patch is against the gettext > version of install-reloc, I am CC'ing this to bug-gnu-gettext. I > don't know why the two versions of install-reloc have diverged -- > perhaps it's time to sync gettext back into gnulib? But the problem

Re: RFC: too aggressive nanosleep replacement on 64 bit Linux?

On Tue, 5 Aug 2014, Paul Eggert wrote: > [CC'ing Thomas Gleixner, who maintains the Linux kernel's POSIX clocks and > timers. Thomas, this thread started at > .] > > Pádraig Brady wrote: > > I noticed that nanosleep() was replac

Re: RFC: too aggressive nanosleep replacement on 64 bit Linux?

[CC'ing Thomas Gleixner, who maintains the Linux kernel's POSIX clocks and timers. Thomas, this thread started at .] Pádraig Brady wrote: I noticed that nanosleep() was replaced on 64 bit Linux ... Should we be more conservat

[PATCH 2/2] sys_select: fix FD_ZERO problem on Solaris 10

* lib/sys_select.in.h: Fix Solaris 10 bug where "#include " followed by "#include " caused FD_ZERO to expand to an expression that invoked memset without necessarily including . The problem was that the first include defined _SYS_TIME_H, causing the second include to short-circuit. Fix a similar p

[PATCH 1/2] accept: document Solaris 10 type glitch

* doc/posix-functions/accept.texi (accept): Mention that Solaris 10 'accept' takes void * last arg, not socklen_t *. --- ChangeLog | 6 ++ doc/posix-functions/accept.texi | 4 2 files changed, 10 insertions(+) diff --git a/ChangeLog b/ChangeLog index bdf743a..43b8fe

fpieee module adds inappropriate compiler flags to CPPFLAGS

Hi, we recently encountered a build failure of Octave on alpha [1,2] due to an added indirect dependency on the fpieee gnulib module, which appends compiler options to CPPFLAGS that don't necessarily belong there. This module apparently adds either "-mieee" or "-ieee" to CPPFLAGS when building on

RFC: too aggressive nanosleep replacement on 64 bit Linux?

I noticed that nanosleep() was replaced on 64 bit Linux which is due to gnulib checking for the full potential 292 billion years on 64 bit time_t but the kernel supporting "only" 292 years due to: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/linux/time.h?id=refs/tags