Source: freetalk
Version: 3.2-4
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:
> g++ -DPACKAGE_NAME=\"freetalk\" -DPACKAGE_TARNAME=\"freetalk\" 
> -DPACKAGE_VERSION=\"3.2\" -DPACKAGE_STRING=\"freetalk\ 3.2\" 
> -DPACKAGE_BUGREPORT=\"[email protected]\" -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"freetalk\" -DVERSION=\"3.2\" -DHAVE_LIBREADLINE=1 
> -DHAVE_LIBGUILE=1 -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_ARGP=1 
> -DHAVE_ERRNO_H=1 -DHAVE_ERROR_T=1 -DENABLE_NLS=1 -DHAVE_GETTEXT=1 
> -DHAVE_DCGETTEXT=1 -DHAVE_ICONV=1 -DICONV_CONST= -I.  -Wall -g  
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include   
> -I/usr/include/loudmouth-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include   -DDATADIR=\"/usr/share\" 
> -DLOCALEDIR=\"/usr/share/locale\"   -g -O2 -MT callbacks.o -MD -MP -MF 
> .deps/callbacks.Tpo -c -o callbacks.o callbacks.cc
> callbacks.cc: In function 'LmHandlerResult 
> ft_msg_msg_handler(LmMessageHandler*, LmConnection*, LmMessage*, void*)':
> callbacks.cc:156: error: assignment of read-only location '* strchr(from, 47)'
> make[2]: *** [callbacks.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/12/10/freetalk_3.2-4_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