[Pkg-ofed-devel] Bug#707398: dapl: FTBFS: dat/common/dat_strerror.c:604:30: error: 'NULL' undeclared (first use in this function)

[Lucas Nussbaum]

Source: dapl
Version: 2.0.19-1.1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130509 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> if /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.    -g -Wall -D_GNU_SOURCE -DDAT_CONF="\"/etc/dat.conf\"" -D_GNU_SOURCE -DOS_RELEASE=131078    -DDAT_EXTENSIONS -I./dat/include/ -I./dat/udat/ -I./dat/udat/linux -I./dat/common/   -MT dat_udat_libdat2_la-dat_strerror.lo -MD -MP -MF ".deps/dat_udat_libdat2_la-dat_strerror.Tpo" -c -o dat_udat_libdat2_la-dat_strerror.lo `test -f 'dat/common/dat_strerror.c' || echo './'`dat/common/dat_strerror.c; \
> 	then mv -f ".deps/dat_udat_libdat2_la-dat_strerror.Tpo" ".deps/dat_udat_libdat2_la-dat_strerror.Plo"; else rm -f ".deps/dat_udat_libdat2_la-dat_strerror.Tpo"; exit 1; fi
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I. -g -Wall -D_GNU_SOURCE -DDAT_CONF=\"/etc/dat.conf\" -D_GNU_SOURCE -DOS_RELEASE=131078 -DDAT_EXTENSIONS -I./dat/include/ -I./dat/udat/ -I./dat/udat/linux -I./dat/common/ -MT dat_udat_libdat2_la-dat_strerror.lo -MD -MP -MF .deps/dat_udat_libdat2_la-dat_strerror.Tpo -c dat/common/dat_strerror.c  -fPIC -DPIC -o .libs/dat_udat_libdat2_la-dat_strerror.o
> dat/common/dat_strerror.c: In function 'dat_strerror':
> dat/common/dat_strerror.c:604:30: error: 'NULL' undeclared (first use in this function)
> dat/common/dat_strerror.c:604:30: note: each undeclared identifier is reported only once for each function it appears in
> make[3]: *** [dat_udat_libdat2_la-dat_strerror.lo] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2013/05/09/dapl_2.0.19-1.1_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.