Source: engauge-digitizer
Version: 4.1-2
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> g++ -c -pipe -g -Wall -W -O0 -Wno-non-virtual-dtor -D_REENTRANT  
> -DDEBIAN_PACKAGE -DQT_THREAD_SUPPORT -I/usr/share/qt3/mkspecs/default -I. 
> -I/usr/include/qt3 -o src/.objs/axispointdlg.o src/axispointdlg.cpp
> In file included from /usr/include/qt3/qmap.h:49:0,
>                  from /usr/include/qt3/qmime.h:46,
>                  from /usr/include/qt3/qevent.h:48,
>                  from /usr/include/qt3/qobject.h:48,
>                  from /usr/include/qt3/qwidget.h:46,
>                  from /usr/include/qt3/qdialog.h:45,
>                  from /usr/include/qt3/qmessagebox.h:45,
>                  from src/axispointdlg.cpp:38:
> /usr/include/qt3/qvaluelist.h:91:13: error: 'ptrdiff_t' does not name a type
> /usr/include/qt3/qvaluelist.h:167:13: error: 'ptrdiff_t' does not name a type
> In file included from /usr/include/qt3/qmap.h:49:0,
>                  from /usr/include/qt3/qmime.h:46,
>                  from /usr/include/qt3/qevent.h:48,
>                  from /usr/include/qt3/qobject.h:48,
>                  from /usr/include/qt3/qwidget.h:46,
>                  from /usr/include/qt3/qdialog.h:45,
>                  from /usr/include/qt3/qmessagebox.h:45,
>                  from src/axispointdlg.cpp:38:
> /usr/include/qt3/qvaluelist.h:427:13: error: 'ptrdiff_t' does not name a type
> In file included from /usr/include/qt3/qmime.h:46:0,
>                  from /usr/include/qt3/qevent.h:48,
>                  from /usr/include/qt3/qobject.h:48,
>                  from /usr/include/qt3/qwidget.h:46,
>                  from /usr/include/qt3/qdialog.h:45,
>                  from /usr/include/qt3/qmessagebox.h:45,
>                  from src/axispointdlg.cpp:38:
> /usr/include/qt3/qmap.h:110:13: error: 'ptrdiff_t' does not name a type
> /usr/include/qt3/qmap.h:226:13: error: 'ptrdiff_t' does not name a type
> In file included from /usr/include/qt3/qmime.h:46:0,
>                  from /usr/include/qt3/qevent.h:48,
>                  from /usr/include/qt3/qobject.h:48,
>                  from /usr/include/qt3/qwidget.h:46,
>                  from /usr/include/qt3/qdialog.h:45,
>                  from /usr/include/qt3/qmessagebox.h:45,
>                  from src/axispointdlg.cpp:38:
> /usr/include/qt3/qmap.h:607:13: error: 'ptrdiff_t' does not name a type
> In file included from src/mmsubs.h:51:0,
>                  from src/digitdef.h:142,
>                  from src/point.h:45,
>                  from src/pointset.h:63,
>                  from src/digitdoc.h:128,
>                  from src/axispointdlg.cpp:41:
> /usr/include/qt3/qimage.h: In member function 'bool 
> QImageTextKeyLang::operator<(const QImageTextKeyLang&) const':
> /usr/include/qt3/qimage.h:61:61: warning: suggest parentheses around '&&' 
> within '||' [-Wparentheses]
> In file included from src/axispointdlg.cpp:41:0:
> src/digitdoc.h: At global scope:
> src/digitdoc.h:227:41: warning: type qualifiers ignored on function return 
> type [-Wignored-qualifiers]
> src/digitdoc.h:230:43: warning: type qualifiers ignored on function return 
> type [-Wignored-qualifiers]
> make[1]: *** [src/.objs/axispointdlg.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/05/02/engauge-digitizer_4.1-2_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