help-gsasl
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Problem with GNULib testsuite with gsasl 1.6.0 on Solaris 9 i386


From: Dagobert Michelsen
Subject: Problem with GNULib testsuite with gsasl 1.6.0 on Solaris 9 i386
Date: Wed, 15 Dec 2010 15:53:47 +0100

Hi,

when I try to compile GNU SASL 1.6.0 on Solaris 9 i386 and also Sparc
with Sun Studio 12 I get the following error when the testsuite for
gnulib is compiled:

> gmake[3]: `test-memchr' is up to date.
> gmake[3]: `test-memmem' is up to date.
> gmake[3]: `test-stdbool' is up to date.
> gmake[3]: `test-stddef' is up to date.
> \
> source='test-stdint.c' object='test-stdint.o' libtool=no \
> DEPDIR=.deps depmode=none /bin/bash ../build-aux/depcomp \
> /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I..  -DIN_LIBGSASL_GNULIB_TESTS=1 
> -I. -I. -I.. -I./.. -I../gl -I./../gl -I/opt/csw/include  -xO3 -m32 
> -xarch=386 -xnorunpath -c test-stdint.c
> "test-stdint.c", line 63: warning: implicit function declaration: INT64_C
> "test-stdint.c", line 63: non-constant initializer: op "CALL"
> "test-stdint.c", line 83: warning: implicit function declaration: UINT64_C
> "test-stdint.c", line 83: non-constant initializer: op "CALL"
> "test-stdint.c", line 240: non-constant initializer: op "CALL"
> "test-stdint.c", line 246: non-constant initializer: op "CALL"
> "test-stdint.c", line 351: non-constant bit-field size
> "test-stdint.c", line 353: non-constant bit-field size
> cc: acomp failed for test-stdint.c
> gmake[3]: *** [test-stdint.o] Error 2
> gmake[3]: Leaving directory 
> `/home/dam/mgar/pkg/gsasl/trunk/work/solaris9-i386/build-isa-i386/gsasl-1.6.0/lib/gltests'
> gmake[2]: *** [check-am] Error 2
> gmake[2]: Leaving directory 
> `/home/dam/mgar/pkg/gsasl/trunk/work/solaris9-i386/build-isa-i386/gsasl-1.6.0/lib/gltests'
> gmake[1]: *** [check-recursive] Error 1
> gmake[1]: Leaving directory 
> `/home/dam/mgar/pkg/gsasl/trunk/work/solaris9-i386/build-isa-i386/gsasl-1.6.0/lib/gltests'
> gmake: *** [check] Error 2

It looks like as if the type is not properly defined. Any insights on this 
already?


Best regards

  -- Dago




reply via email to

[Prev in Thread] Current Thread [Next in Thread]