Albert Chin <bug-gnu...@mlists.thewrittenword.com> writes:
> With latest gnulib on HP-UX 10.20:
> $ ./gnulib-tool --create-testdir --dir=t strtoull
> $ cd t
> $ ./configure
> ...
> $ gmake
> ...
> source='dummy.c' object='dummy.o' libtool=no \
> DEPDIR=.deps depmode=hp /bin/sh ../build-aux/depcomp \
> cc -Ae -DHAVE_CONFIG_H -I. -I.. -g -c dummy.c
> source='strtoull.c' object='strtoull.o' libtool=no \
> DEPDIR=.deps depmode=hp /bin/sh ../build-aux/depcomp \
> cc -Ae -DHAVE_CONFIG_H -I. -I.. -g -c strtoull.c
> cpp: "stdlib.h", line 52: error 4036: Can't open include file 'stdint.h'.
> gmake[4]: *** [strtoull.o] Error 1
stdlib.in.h needs stdint.h for struct random_data:
struct random_data
{
int32_t *fptr; /* Front pointer. */
...
So either we do:
--- a/modules/stdlib
+++ b/modules/stdlib
@@ -9,6 +9,7 @@ Depends-on:
include_next
link-warning
unistd
+stdint
Or we add a new module 'random_data' that depends on stdlib+stdint, and
makes stdlib.h include stdint.h and define struct random_data.
I can see the advantages in the second alternative, to avoid having
gnulib's stdlib.h depend on stdint.h, but in the long run I'm not sure
if it is worth it.
Thoughts?
/Simon
