Hi Roland, Thanks for your bugreport. Ko van der Sloot and me are working on the issue. The issue will get fixed in a next release.
Bye, Joost On Tue, Feb 12, 2013 at 11:12:33AM +0100, Roland Stigge wrote: > Package: timbl > Version: 6.4.3-1 > Severity: serious > Tags: sid > User: [email protected] > Usertags: powerpcspe > > Hi, > > trying to build frog[1] on powerpcspe[2], I got this result[3]: > > make[3]: Entering directory `/«PKGBUILDDIR»/build/2.6/src' > g++ -DHAVE_CONFIG_H -I. -I/«PKGBUILDDIR»/./src -I.. > -I/«PKGBUILDDIR»/./include -g -O2 -fstack-protector > --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -pthread > -fopenmp -I/usr/include -I/usr/include/libxml2 -I/usr/include/libxml2 > -I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 > -I/usr/include/python2.7 -c -o mbma_mod.o /«PKGBUILDDIR»/./src/mbma_mod.cxx > In file included from /usr/include/timbl/TimblAPI.h:37:0, > from /«PKGBUILDDIR»/./src/mbma_mod.cxx:34: > /usr/include/timbl/Types.h:42:33: fatal error: ticcutils/StringOps.h: No such > file or directory > compilation terminated. > > Looks like /usr/include/timbl/Types.h in libtimbl3-dev references > ticcutils/StringOps.h from libticcutils1-dev but doesn't depend on it. > > You can reproduce this issue with a simple test program like: > > #include <timbl/Types.h> > int main() { return 0; } > > Just checked that the frog FTBFS issue is also present in amd64. > > Adding the libticcutils1-dev fixes this. However, is appears that further, > frog > also uses timbl/LogStream.h which isn't (anymore?) in libtimbl3-dev. > > Thanks in advance, > > Roland > > > [1] http://packages.qa.debian.org/f/frog.html > [2] http://wiki.debian.org/PowerPCSPEPort > [3] http://buildd.debian-ports.org/status/package.php?p=frog > > -- System Information: > Debian Release: 7.0 > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
