Re: sys-limits.h on illumos

2019-01-03 Thread Paul Eggert
I looked for similar problems on Solaris 11 and found a couple of potential name clashes, fixed as per attached. >From df8874aaf70104f80dd83e27de73bdb6951dfb39 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Thu, 3 Jan 2019 22:36:21 -0800 Subject: [PATCH] bitset, crypto/gc: fix conflicts with So

Re: sys-limits.h on illumos

2019-01-03 Thread Bruno Haible
Hi, Andy Fiddaman wrote: > There's a compatibility problem with the guard definition used in the > sys-limits.h file that affects illumos (an opensolaris derivative) and most > likely Solaris too. > > These operating systems have a /usr/include/sys/limits.h file which uses the > _SYS_LIMITS_H gua

sys-limits.h on illumos

2019-01-03 Thread Andy Fiddaman
There's a compatibility problem with the guard definition used in the sys-limits.h file that affects illumos (an opensolaris derivative) and most likely Solaris too. These operating systems have a /usr/include/sys/limits.h file which uses the _SYS_LIMITS_H guard. Since the same guard is used in

Re: closed file descriptors on HP-UX

2019-01-03 Thread Bruno Haible
Paul Eggert asks: > > On HP-UX 11.31, however, the exec() call transforms a closed file > > descriptor to a file descriptor that behaves identically to /dev/null, > > regarding fstat and fcntl. > > Does this happen for all file decriptors, or only for file descriptors 0, 1, > and > 2? Only for

Re: closed file descriptors on HP-UX

2019-01-03 Thread Paul Eggert
Bruno Haible wrote: On HP-UX 11.31, however, the exec() call transforms a closed file descriptor to a file descriptor that behaves identically to /dev/null, regarding fstat and fcntl. Does this happen for all file decriptors, or only for file descriptors 0, 1, and 2? If the latter, then HP-UX

closed file descriptors on HP-UX

2019-01-03 Thread Bruno Haible
This is a note about a portability pitfall regarding closed file descriptors. Spotted while investigating a diffutils test failure [1]. Such closed file descriptors can be "created" through the shell syntax <&- and >&- , as specified by POSIX (section 2.7.5 of [2]). The issue = On most p

Re: nested functions

2019-01-03 Thread Bruno Haible
[Not sure this is the right forum. Maybe stackoverflow.com would be a better place to discuss this.] Tim Rühsen wrote: > BTW, nested functions are pretty nice to use. > > But I still wonder why > > - nested functions need an executable stack (why does the code have to > be run on the stack ?)

Re: [RFC] Adding a real HashTable implementation to gnulib

2019-01-03 Thread Tim Rühsen
On 12/4/18 3:32 AM, Bruno Haible wrote: > Hi Tim, > >> We have 'hashmap' [1] in GNU Wget2. > > Things I like about the implementation: > > - Collision resolution through linked list (a robust algorithm). > > - Reasonably generic API. > > - The user-definable destructor functions. > > Th

Re: how to build gnulib for shared libraries?

2019-01-03 Thread Szabolcs Nagy
On 20/12/2018 03:18, Bruno Haible wrote: > Hi Szabolcs, > > (or should I say "Hi Nagy"? Sorry, with Hungarian proper names, I never > know what is the surname and what is the given name.) (szabolcs is my given name, i only use the hungarian order in hungarian language context) >> by default gnul

Re: [PATCH v3 0/2] Fix syntax-check on macOS/FreeBSD

2019-01-03 Thread Eric Blake
On 1/3/19 8:44 AM, Eric Blake wrote: > And I botched something in _sc_search_regexp. Will push the followup > patch as soon as I diagnose the issue. > D'oh, I killed an important backslash: +++ b/top/maint.mk @@ -314,7 +314,7 @@ define _sc_search_regexp : Check for the construct;

Re: [PATCH v3 0/2] Fix syntax-check on macOS/FreeBSD

2019-01-03 Thread Eric Blake
On 1/2/19 2:14 PM, Eric Blake wrote: > On 12/20/18 7:06 AM, Roman Bolshakov wrote: >> On Thu, Dec 13, 2018 at 06:34:51PM +0300, Roman Bolshakov wrote: >>> Hello, >>> >>> There was an issue with syntax-check on FreeBSD reported a few years >>> ago: >>> https://www.redhat.com/archives/libvir-list/201