Re: lock, tls, and single-threaded applications

Eric Blake wrote: > Next I'm wondering if we should add a module which invokes > gl_DISABLE_THREADS, as well as pulls in the unlocked-io module, for the > benefit of projects that are known to be single-threaded, as it is > slightly easier to add a module to the list of imports than it is to > modi

update article url

Pushed. /Simon diff --git a/ChangeLog b/ChangeLog index 696c961..95f13fe 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2008-06-18 Simon Josefsson <[EMAIL PROTECTED]> + + * users.txt: Update URL to article and add author/date + information. + 2008-06-17 Bruno Haible <[EM

Re: lock, tls, and single-threaded applications

Bruno Haible <[EMAIL PROTECTED]> wrote: > Eric Blake wrote: >> Next I'm wondering if we should add a module which invokes >> gl_DISABLE_THREADS, as well as pulls in the unlocked-io module, for the >> benefit of projects that are known to be single-threaded, as it is >> slightly easier to add a modu

strsignal on cygwin

Cygwin 1.5.25 and earlier provides strsignal that returns const char *; at the time cygwin added strsignal, it was not standardized. Now, POSIX 200x is adding strsignal, but chose to follow glibc's convention of returning char* rather than cygwin's const char *. I've posted a patch to cygwin 1

Re: POSIX in docs [was: RFC: sigaction module]

Paul had a preference for "Posix" Paul? I have seen "POSIX" far more than any other spelling. "Posix" just looks wrong to me. Maybe in 20 years it'll look right, the way "Fortran" does now ... As far as Texinfo goes, I recommend just writing it as-is with no markup. I see no significant

Re: POSIX in docs

[EMAIL PROTECTED] (Karl Berry) writes: > Paul had a preference for "Posix" > > Paul? > > I have seen "POSIX" far more than any other spelling. Yes, and "UNIX" is more common than "Unix", and "FORTRAN" used to be more common than "Fortran". Here's an idea: RMS invented the term "POSIX"/"Posi

POSIX vs. Posix

rms -- we've discovered that different GNU manuals spell use different spellings for POSIX. Since you invented the term, we thought we'd ask you: do you have a preference for one of "POSIX" or "Posix"? And, a second question if the answer is "POSIX": for Texinfo, do you have a preference for @acr

Re: strsignal on cygwin

Eric Blake wrote: > Why POSIX didn't make the return type const char* is beyond me. Probably because the return type was already 'char *' on glibc systems, MacOS X, FreeBSD, OpenBSD, NetBSD, AIX 5.1, Solaris. And 'const char *' only on Cygwin. Bruno

Re: psiginfo

Eric Blake wrote: > Meanwhile, I'm looking at the POSIX definition of psiginfo, and wondering how > on earth it is intended to be used! psiginfo is intentionally omitted from > the > list of async-signal-safe functions, but you only ever get a populated > siginfo_t* in the context of a signal

Re: lock, tls, and single-threaded applications

Jim Meyering wrote: > That has made me consider (if/when sort does become > multithreaded) building specified multithreaded programs in > coreutils against a separate thread-safe gnulib instance, > so that the remaining 100 programs don't suffer just because > sort flipped the MT switch. Makes sen

Re: strsignal on cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 6/18/2008 6:21 PM: | Eric Blake wrote: |> Why POSIX didn't make the return type const char* is beyond me. | | Probably because the return type was already 'char *' on glibc systems, | MacOS X, FreeBSD, OpenBSD, NetBSD, AIX

Re: sigaction, SA_SIGINFO, and SIG_IGN

Eric Blake wrote: > | POSIX is not correct about the type of SIG_DFL and SIG_IGN: > | In it says > | "... constants, each of which expands to a distinct constant expression > of > |the type void (*)(int) ...: SIG_DFL SIG_IGN" > | but

RE: sigaction, SA_SIGINFO, and SIG_IGN

>The include files of all systems that I have access to contain sa_handler and >sa_sigaction as elements of the same union, i.e. they overlap. Only Interix 3.5 >has a struct sigaction that lacks the 'sa_sigaction' member. But don't waste >your time on that system, it's not worth porting to. Sez yo

Re: Infinite loop on make dist

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 6/18/2008 10:05 PM: | According to Stepan Kasal on 6/18/2008 9:50 PM: | | Hello, | | when I unpack autoconf-2.62.tar.lzma and do | | | | cd autoconf-2.62 | | mkdir build | | cd build | | ../configure && make dist | | | | I