Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Failed to emerge app-i18n/pyzy-0.1.0 [Solved]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
helio
Tux's lil' helper
Tux's lil' helper


Joined: 08 Apr 2006
Posts: 136

PostPosted: Tue Apr 02, 2013 8:36 pm    Post subject: Failed to emerge app-i18n/pyzy-0.1.0 [Solved] Reply with quote

>>> Unpacking source...
>>> Unpacking pyzy-0.1.0.tar.gz to /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work
>>> Unpacking pyzy-database-1.0.0.tar.bz2 to /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work
>>> Source unpacked in /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work
>>> Preparing source in /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0 ...
* Applying pyzy-dont-download-dictionary-file.patch ...
 [ ok ]
* Converting shebang in '/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db/android/create_db.py'
* Running eautoreconf in '/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0' ...
* Running libtoolize --install --copy --force --automake ...
 [ ok ]
* Running aclocal -I m4 ...
 [ ok ]
* Running autoconf ...
 [ ok ]
* Running autoheader ...
 [ ok ]
* Running automake --add-missing --copy ...
 [ ok ]
* Running elibtoolize in: pyzy-0.1.0/
* Applying portage/1.2.0 patch ...
* Applying sed/1.5.6 patch ...
* Applying as-needed/2.2.6 patch ...
>>> Source prepared.
>>> Configuring source in /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0 ...
* econf: updating pyzy-0.1.0/config.guess with /usr/share/gnuconfig/config.guess
* econf: updating pyzy-0.1.0/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-silent-rules --disable-dependency-tracking --enable-db-open-phrase --enable-db-android --disable-boost --disable-opencc --disable-tests
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for style of include used by make... GNU
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... none
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking whether make supports nested variables... yes
checking whether build environment is sane... yes
checking for x86_64-pc-linux-gnu-gcc... (cached) x86_64-pc-linux-gnu-gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... (cached) yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... (cached) none needed
checking dependency style of x86_64-pc-linux-gnu-gcc... (cached) none
checking for x86_64-pc-linux-gnu-g++... x86_64-pc-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-pc-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-pc-linux-gnu-g++... none
checking whether x86_64-pc-linux-gnu-gcc and cc understand -c and -o together... yes
checking for library containing strerror... none required
checking for ANSI C header files... (cached) yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 3458764513820540925
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump
checking how to recognize dependent libraries... pass_all
checking for x86_64-pc-linux-gnu-dlltool... no
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for archiver @FILE support... @
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok
checking for sysroot... no
checking for x86_64-pc-linux-gnu-mt... no
checking for mt... no
checking if : is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... (cached) yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... x86_64-pc-linux-gnu-g++ -E
checking for ld used by x86_64-pc-linux-gnu-g++... /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for x86_64-pc-linux-gnu-g++ option to produce PIC... -fPIC -DPIC
checking if x86_64-pc-linux-gnu-g++ PIC flag -fPIC -DPIC works... yes
checking if x86_64-pc-linux-gnu-g++ static flag -static works... yes
checking if x86_64-pc-linux-gnu-g++ supports -c -o file.o... yes
checking if x86_64-pc-linux-gnu-g++ supports -c -o file.o... (cached) yes
checking whether the x86_64-pc-linux-gnu-g++ linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for x86_64-pc-linux-gnu-pkg-config... /usr/bin/x86_64-pc-linux-gnu-pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.0.0... yes (version 2.32.4)
checking for GLIB2... yes
checking for SQLITE... yes
checking for sqlite3... /usr/bin/sqlite3
checking for uuid_create... no
checking for LIBUUID... yes
checking for env... /usr/bin/env
checking for doxygen... no
configure: WARNING: Doxygen not found - continuing without Doxygen support
configure: creating ./config.status
config.status: creating Makefile
config.status: creating data/Makefile
config.status: creating data/db/Makefile
config.status: creating data/db/android/Makefile
config.status: creating data/db/open-phrase/Makefile
config.status: creating docs/Makefile
config.status: creating m4/Makefile
config.status: creating pyzy-1.0.pc
config.status: WARNING: 'pyzy-1.0.pc.in' seems to ignore the --datarootdir setting
config.status: creating pyzy.spec
config.status: creating src/Makefile
config.status: creating src/tests/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands

Build options:
Version 0.1.0
Install prefix /usr
Use boost no
Use opencc no
Build database android yes
Build database open-phrase yes
Run test cases no

>>> Source configured.
>>> Compiling source in /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0 ...
make -j9
(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/missing --run autoheader)
rm -f stamp-h1
touch config.h.in
cd . && /bin/sh ./config.status config.h
config.status: creating config.h
config.status: config.h is unchanged
make all-recursive
make[1]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0'
Making all in data
make[2]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data'
Making all in db
make[3]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db'
Making all in android
make[4]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db/android'
\
rm -f android.db; \
./create_db.py ./rawdict_utf16_65105_freq.txt | /usr/bin/sqlite3 android.db || \
( rm -f android.db ; exit 1 )
make[4]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db/android'
Making all in open-phrase
make[4]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db/open-phrase'
\
tar jxfm pyzy-database-1.0.0.tar.bz2; \
mv db/main.db db/open-phrase.db; \
touch stamp-db
tar (child): pyzy-database-1.0.0.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
make[4]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db/open-phrase'
make[4]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db'
make[3]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data/db'
make[3]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data'
make[2]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/data'
Making all in docs
make[2]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/docs'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/docs'
Making all in m4
make[2]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/m4'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/m4'
Making all in src
make[2]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/src'
make all-recursive
make[3]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/src'
make[4]: Entering directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/src'
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-BopomofoContext.lo `test -f 'BopomofoContext.cc' || echo './'`BopomofoContext.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-Database.lo `test -f 'Database.cc' || echo './'`Database.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-DoublePinyinContext.lo `test -f 'DoublePinyinContext.cc' || echo './'`DoublePinyinContext.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-DynamicSpecialPhrase.lo `test -f 'DynamicSpecialPhrase.cc' || echo './'`DynamicSpecialPhrase.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-FullPinyinContext.lo `test -f 'FullPinyinContext.cc' || echo './'`FullPinyinContext.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-InputContext.lo `test -f 'InputContext.cc' || echo './'`InputContext.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-PhoneticContext.lo `test -f 'PhoneticContext.cc' || echo './'`PhoneticContext.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-PhraseEditor.lo `test -f 'PhraseEditor.cc' || echo './'`PhraseEditor.cc
/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c -o libpyzy_1_0_la-PinyinContext.lo `test -f 'PinyinContext.cc' || echo './'`PinyinContext.cc
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c FullPinyinContext.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-FullPinyinContext.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c BopomofoContext.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-BopomofoContext.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c PhraseEditor.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-PhraseEditor.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c PhoneticContext.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-PhoneticContext.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c Database.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-Database.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c InputContext.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-InputContext.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c DoublePinyinContext.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-DoublePinyinContext.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c DynamicSpecialPhrase.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-DynamicSpecialPhrase.o
libtool: compile: x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -DPKGDATADIR=\"/usr/share/pyzy\" -std=c++0x -I/usr/include/uuid -O2 -pipe -c PinyinContext.cc -fPIC -DPIC -o .libs/libpyzy_1_0_la-PinyinContext.o
In file included from Database.cc:22:0:
Database.h: In static member function 'static PyZy::Database& PyZy::Database::instance()':
Database.h:82:27: error: no match for 'operator==' in 'PyZy::Database::m_instance == 0l'
Database.h:82:27: note: candidate is: operator==(int, long int) <built-in>
In file included from PhraseEditor.cc:25:0:
Database.h: In static member function 'static PyZy::Database& PyZy::Database::instance()':
Database.h:82:27: error: no match for 'operator==' in 'PyZy::Database::m_instance == 0l'
Database.h:82:27: note: candidate is: operator==(int, long int) <built-in>
In file included from PhoneticContext.cc:24:0:
Database.h: In static member function 'static PyZy::Database& PyZy::Database::instance()':
Database.h:82:27: error: no match for 'operator==' in 'PyZy::Database::m_instance == 0l'
Database.h:82:27: note: candidate is: operator==(int, long int) <built-in>
make[4]: *** [libpyzy_1_0_la-PhraseEditor.lo] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: *** [libpyzy_1_0_la-PhoneticContext.lo] Error 1
make[4]: *** [libpyzy_1_0_la-Database.lo] Error 1
In file included from InputContext.cc:28:0:
Database.h: In static member function 'static PyZy::Database& PyZy::Database::instance()':
Database.h:82:27: error: no match for 'operator==' in 'PyZy::Database::m_instance == 0l'
Database.h:82:27: note: candidate is: operator==(int, long int) <built-in>
make[4]: *** [libpyzy_1_0_la-InputContext.lo] Error 1
make[4]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0'
make: *** [all] Error 2
* ERROR: app-i18n/pyzy-0.1.0 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=app-i18n/pyzy-0.1.0'`,
* the complete build log and the output of `emerge -pqv '=app-i18n/pyzy-0.1.0'`.
* The complete build log is located at '/var/log/portage/app-i18n:pyzy-0.1.0:20130402-202748.log'.
* For convenience, a symlink to the build log is located at '/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/temp/build.log'.
* The ebuild environment file is located at '/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/temp/environment'.
* Working directory: '/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0'
* S: '/scratch/var/tmp/portage/app-i18n/pyzy-0.1.0/work/pyzy-0.1.0'


Last edited by helio on Sun Apr 07, 2013 6:38 am; edited 1 time in total
Back to top
View user's profile Send private message
Moult
Developer
Developer


Joined: 31 Mar 2008
Posts: 110
Location: Malaysia

PostPosted: Fri Apr 05, 2013 10:23 pm    Post subject: Reply with quote

"Me too!"

Submitted bug report: https://bugs.gentoo.org/show_bug.cgi?id=464778
_________________
thinkMoult - blog and stuff
WIPUP - share your works-in-progress for long-term, ambitious projects.
Back to top
View user's profile Send private message
helio
Tux's lil' helper
Tux's lil' helper


Joined: 08 Apr 2006
Posts: 136

PostPosted: Sat Apr 06, 2013 1:39 am    Post subject: Reply with quote

Moult wrote:
"Me too!"

Submitted bug report: https://bugs.gentoo.org/show_bug.cgi?id=464778


Thanks for submitting the bug report. I have app-i18n/pyzy installed in several desktops/laptops of mine, but only one of them has this problem.
Back to top
View user's profile Send private message
dlan
n00b
n00b


Joined: 07 Apr 2013
Posts: 2

PostPosted: Sun Apr 07, 2013 5:12 am    Post subject: Re: Failed to emerge app-i18n/pyzy-0.1.0 Reply with quote

hello, I can't reproduce this.
could you please post me your "emerge --info =app-i18n/pyzy-0.1.0"

please keep your eyes on the bug id in bugzilla,
I'll tracking there

also I've posted a patch there to try to fix this problem, please help and test..

thanks
Back to top
View user's profile Send private message
Moult
Developer
Developer


Joined: 31 Mar 2008
Posts: 110
Location: Malaysia

PostPosted: Sun Apr 07, 2013 6:17 am    Post subject: Reply with quote

Seems it was fixed by upgrading from gcc-4.5.4 to gcc-4.6.3. @helio, can you confirm if this fix is the same for you?
_________________
thinkMoult - blog and stuff
WIPUP - share your works-in-progress for long-term, ambitious projects.
Back to top
View user's profile Send private message
dlan
n00b
n00b


Joined: 07 Apr 2013
Posts: 2

PostPosted: Sun Apr 07, 2013 6:20 am    Post subject: Re: Failed to emerge app-i18n/pyzy-0.1.0 Reply with quote

@helio
we found that upgrading gcc (at least to 4.6.3) could fix this problem,
please help test and confirm (refer the bugz for detail)
thanks
Back to top
View user's profile Send private message
helio
Tux's lil' helper
Tux's lil' helper


Joined: 08 Apr 2006
Posts: 136

PostPosted: Sun Apr 07, 2013 6:37 am    Post subject: Re: Failed to emerge app-i18n/pyzy-0.1.0 Reply with quote

dlan wrote:
@helio
we found that upgrading gcc (at least to 4.6.3) could fix this problem,
please help test and confirm (refer the bugz for detail)
thanks


Confirmed! Thanks so much, Moult and dlan.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum