Source: tclx8.4
Version: 8.4.0-3.1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20140329 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -pipe -DPACKAGE_NAME=\"tclx\" -DPACKAGE_TARNAME=\"tclx\" 
> -DPACKAGE_VERSION=\"8.4\" -DPACKAGE_STRING=\"tclx\ 8.4\" 
> -DPACKAGE_BUGREPORT=\"\" -DFULL_VERSION=\"8.4.0\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 -DUSE_THREAD_ALLOC=1 
> -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 -DSTATIC_BUILD=1 
> -D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_IS_LONG=1 -DUSE_TCL_STUBS=1 
> -DHAVE_SYS_SELECT_H=1 -DRETSIGTYPE=void -DHAVE_SYS_TIME_H=1 
> -DTIME_WITH_SYS_TIME=1 -DHAVE_STRUCT_TM_TM_ZONE=1 -DHAVE_TM_ZONE=1 
> -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 -DHAVE_TM_GMTOFF=1 
> -DHAVE_TIMEZONE_VAR=1  -I"./generic" -I"./unix" 
> -I"/usr/include/tcl8.6/tcl-private/generic" 
> -I"/usr/include/tcl8.6/tcl-private/unix"    -Wall -g -O2 -O2 
> -fomit-frame-pointer -Wall -Wno-implicit-int -c `echo 
> ./generic/tclXgeneral.c` -o tclXgeneral.o
> ./generic/tclXgeneral.c: In function 'TclX_LoopObjCmd':
> ./generic/tclXgeneral.c:408:10: error: 'Tcl_Interp' has no member named 
> 'errorLine'
>     interp->errorLine);
>           ^
> make[1]: *** [tclXgeneral.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/03/29/tclx8.4_8.4.0-3.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.


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

Reply via email to