Source: necpp
Version: 1.4.0+cvs20091005-1
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20091210 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=CXX --mode=compile x86_64-linux-gnu-g++ 
> -DHAVE_CONFIG_H -I. -I. -I..     -Wall -g -O2 -MT libnecpp_la-c_geometry.lo 
> -MD -MP -MF ".deps/libnecpp_la-c_geometry.Tpo" -c -o 
> libnecpp_la-c_geometry.lo `test -f 'c_geometry.cpp' || echo 
> './'`c_geometry.cpp; \
>       then mv -f ".deps/libnecpp_la-c_geometry.Tpo" 
> ".deps/libnecpp_la-c_geometry.Plo"; else rm -f 
> ".deps/libnecpp_la-c_geometry.Tpo"; exit 1; fi
> libtool: compile:  x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -Wall -g 
> -O2 -MT libnecpp_la-c_geometry.lo -MD -MP -MF 
> .deps/libnecpp_la-c_geometry.Tpo -c c_geometry.cpp  -fPIC -DPIC -o 
> .libs/libnecpp_la-c_geometry.o
> c_geometry.cpp: In member function 'void 
> c_geometry::geometry_complete(nec_context*, int, int)':
> c_geometry.cpp:506: error: 'uint32_t' was not declared in this scope
> c_geometry.cpp:506: error: expected ';' before 'i'
> c_geometry.cpp:506: error: 'i' was not declared in this scope
> c_geometry.cpp:509: error: expected ';' before 'j'
> c_geometry.cpp:509: error: 'j' was not declared in this scope
> make[3]: *** [libnecpp_la-c_geometry.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/10/necpp_1.4.0+cvs20091005-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to