Open GoogleCodeExporter opened 9 years ago
I tested with the 24th version and still same error
./configure: line 2743: syntax error near unexpected token `0.40.0'
./configure: line 2743: `IT_PROG_INTLTOOL(0.40.0)'
any idea ?
Original comment by photocop...@gmail.com
on 31 Mar 2010 at 7:47
Test with "sudo apt-get install intltool"
Original comment by david.ll...@gmail.com
on 7 Apr 2010 at 10:44
Thanks
I dit it already but I have another problem
~/mtool$ ./configure --prefix=/usr
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 NLS is requested... yes
checking for style of include used by make... GNU
checking for gcc... 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 gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for intltool >= 0.40.0... 0.41.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.10.1
checking for XML::Parser... ok
checking how to run the C preprocessor... 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 locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... (cached) /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for nfc_connect in -lnfc... yes
checking for mifare_classic_connect in -lfreefare... yes
checking for g_thread_init in -lgthread-2.0... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DEPS... yes
checking for stdlib.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
configure: creating ./config.status
config.status: error: cannot find input file: `po/Makefile.in.in'
Any idea ?
Original comment by photocop...@gmail.com
on 7 Apr 2010 at 9:31
I too have the same problem.
I copied the po / Makefile po / Makefile.in.in ... but then you have more errors
Original comment by zamby....@gmail.com
on 29 Jul 2010 at 11:06
You have to do ./autogen-sh and later do
intltoolize --force
./configure
make
aaaaaaaaaaaaand i have a problem with thread/Runeable.h
Original comment by Alexx...@gmail.com
on 15 Aug 2011 at 7:08
Original issue reported on code.google.com by
photocop...@gmail.com
on 29 Mar 2010 at 9:58