-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm still working on improving the async-safety in my proposed sigaction
module, and found that it would somewhat easier if I could learn accurate
signal information even when a signal is blocked. Is this okay to apply?
- --
Don't work too hard, mak
Bruno Haible <[EMAIL PROTECTED]> writes:
> This will not compile on Interix 3.5, whereas the current code does.
True; how about working around that problem by inserting the following
prelude into fatal-signal.c:
typedef void (*sa_handler_t) (int);
/* Return the handler of a signal, as a s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 6/20/2008 12:41 PM:
| Bruno Haible <[EMAIL PROTECTED]> writes:
|
|> This will not compile on Interix 3.5, whereas the current code does.
|
| True; how about working around that problem by inserting the following
| prelude i
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"?
I don't care.
Bruno Haible clisp.org> writes:
> > I've gone ahead and done an reduced implementation of sigaction for mingw,
> > getting the parts that were easy to implement and which were exercised
within
> > other gnulib modules.
>
> That's fully sufficient. Nice work!
Your review hopefully made it even
On HP-UX 10.20 with the HP 10.20 C compiler:
$ ./gnulib-tool --test --with-tests stdint
...
cc -Ae -DHAVE_CONFIG_H -I. -I../../gltests -I. -I../../gltests -I..
-I../../gltests/.. -I../gllib -I../../gltests/../gllib-g -c
../../gltests/test-stdint.c
cpp: "test-stdint.c", line
Trying to run the testsuite for the vasprintf-posix module on HP-UX
10.20 using the HP C compiler:
$ ./gnulib-tool --test --with-tests vasprintf-posix
...
PASS: test-EOVERFLOW
PASS: test-alloca-opt
PASS: test-frexp
../../gltests/test-frexpl.c:120: assertion failed
sh[9]: 22438 Abort(c
On Redhat 7.1, Redhat 9, and RHEL 2.1 with the default compiler:
$ ./gnulib-tool --test --with-tests fseeko ftello
...
PASS: test-binary-io.sh
../../gltests/test-fseeko.c:58: assertion failed
../../gltests/test-fseeko.sh: line 3: 10800 Aborted
./test-fseeko${EXEEXT} 1 <"$srcdir/test-fse
Albert Chin wrote:
> On HP-UX 10.20 with the HP 10.20 C compiler:
> $ ./gnulib-tool --test --with-tests stdint
> ...
> cc -Ae -DHAVE_CONFIG_H -I. -I../../gltests -I. -I../../gltests
> -I.. -I../../gltests/.. -I../gllib -I../../gltests/../gllib-g -c
> ../../gltests/test-stdint.
Hi Paul,
> how about working around that problem by inserting the following
> prelude into fatal-signal.c:
>
>typedef void (*sa_handler_t) (int);
>
>/* Return the handler of a signal, as a sa_handler_t value regardless
> of its true type. The resulting function can be compared to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 6/20/2008 5:58 PM:
|> The problem is the following:
|> #if INTMAX_MIN && INTMAX_MAX && UINTMAX_MAX
|
| Well, it seems this compiler does not grok long long numbers in preprocessor
| expressions. But this is an ISO C 99 r
11 matches
Mail list logo