Source: scim-uim
Version: 0.2.0-3
Severity: serious
Tags: squeeze sid
User: [email protected]
Usertags: qa-ftbfs-20100725 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory 
> `/build/user-scim-uim_0.2.0-3-amd64-4vNeWu/scim-uim-0.2.0/src'
> /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
> -I.. -I.. -I../src -DSCIM_ICONDIR=\"/usr/share/scim/icons\" 
> -DSCIM_UIM_ICON_FILE=\"/usr/share/scim/icons/scim-uim.png\"   
> -I/usr/include/scim-1.0    -I/usr/include/uim   -g -O2 -W -g -O -MT 
> uim_la-scim_uim_imengine.lo -MD -MP -MF .deps/uim_la-scim_uim_imengine.Tpo -c 
> -o uim_la-scim_uim_imengine.lo `test -f 'scim_uim_imengine.cpp' || echo 
> './'`scim_uim_imengine.cpp
> mkdir .libs
>  g++ -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -I../src 
> -DSCIM_ICONDIR=\"/usr/share/scim/icons\" 
> -DSCIM_UIM_ICON_FILE=\"/usr/share/scim/icons/scim-uim.png\" 
> -I/usr/include/scim-1.0 -I/usr/include/uim -g -O2 -W -g -O -MT 
> uim_la-scim_uim_imengine.lo -MD -MP -MF .deps/uim_la-scim_uim_imengine.Tpo -c 
> scim_uim_imengine.cpp  -fPIC -DPIC -o .libs/uim_la-scim_uim_imengine.o
> scim_uim_imengine.cpp: In member function 'virtual void 
> UIMInstance::select_candidate(unsigned int)':
> scim_uim_imengine.cpp:443: warning: comparison between signed and unsigned 
> integer expressions
> scim_uim_imengine.cpp: In member function 'virtual void 
> UIMInstance::lookup_table_page_down()':
> scim_uim_imengine.cpp:476: warning: comparison between signed and unsigned 
> integer expressions
> scim_uim_imengine.cpp: In static member function 'static void 
> UIMInstance::uim_cand_select_cb(void*, int)':
> scim_uim_imengine.cpp:804: warning: comparison between signed and unsigned 
> integer expressions
> mv -f .deps/uim_la-scim_uim_imengine.Tpo .deps/uim_la-scim_uim_imengine.Plo
> /bin/bash ../libtool --tag=CXX   --mode=link g++ -I/usr/include/scim-1.0    
> -I/usr/include/uim   -g -O2 -W -g -O -avoid-version -rpath 
> /usr/lib/scim-1.0/1.4.0/IMEngine -module -export-symbols-regex "^[^_].*" 
> -lscim-1.0 -luim-scm -luim    -o uim.la -rpath 
> /usr/lib/scim-1.0/1.4.0/IMEngine uim_la-scim_uim_imengine.lo  
> generating symbol list for `uim.la'
> /usr/bin/nm -B  .libs/uim_la-scim_uim_imengine.o  | sed -n -e 's/^.*[         
> ]\([ABCDGIRSTW][ABCDGIRSTW]*\)[         ][      
> ]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | /bin/sed 's/.* //' | sort | uniq 
> > .libs/uim.exp
> /bin/grep -E -e "^[^_].*" ".libs/uim.exp" > ".libs/uim.expT"
> mv -f ".libs/uim.expT" ".libs/uim.exp"
> g++ -shared -nostdlib 
> /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/4.4.4/crtbeginS.o  
> .libs/uim_la-scim_uim_imengine.o  /usr/lib/libscim-1.0.so -luim-scm -luim 
> -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4 
> -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib -L/lib/../lib 
> -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../.. -lstdc++ -lm 
> -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/4.4.4/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/4.4.4/../../../../lib/crtn.o  -Wl,-soname 
> -Wl,uim.so -Wl,-retain-symbols-file -Wl,.libs/uim.exp -o .libs/uim.so
> creating uim.la
> /bin/sed: can't read /usr/lib/libltdl.la: No such file or directory
> libtool: link: `/usr/lib/libltdl.la' is not a valid libtool archive
> make[3]: *** [uim.la] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2010/07/25/scim-uim_0.2.0-3_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