[Dovecot] ImapTest build problem
Hello.
My system is: Debian Lenny 2.6.26-2-amd64
I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation
But get this:
./configure --with-dovecot=../dovecot-2.0.beta4 && make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
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 ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
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 dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
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 how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/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... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating stamp.h
config.status: creating imaptest-config.h
config.status: imaptest-config.h is unchanged
config.status: executing depfiles commands
make all-recursive
make[1]: Entering directory /root/imaptest-20100221' Making all in src make[2]: Entering directory
/root/imaptest-20100221/src'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/root/dovecot-2.0.beta4
-I/root/dovecot-2.0.beta4/src/lib -I/root/dovecot-2.0.beta4/src/lib-mail
-I/root/dovecot-2.0.beta4/src/lib-imap -g -O2 -MT client.o -MD -MP -MF
".deps/client.Tpo" -c -o client.o client.c;
then mv -f ".deps/client.Tpo" ".deps/client.Po"; else rm -f
".deps/client.Tpo"; exit 1; fi
client.c: In function ‘client_enabled’:
client.c:178: warning: assignment makes pointer from integer without a cast
client.c: In function ‘client_vanished’:
client.c:203: error: called object ‘3’ is not a function
client.c:207: warning: passing argument 1 of ‘strlen’ makes pointer from
integer without a cast
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: passing argument 1 of ‘__builtin_strcmp’ makes
pointer from integer without a cast
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: passing argument 1 of ‘strlen’ makes pointer from
integer without a cast
client.c:207: warning: passing argument 1 of ‘__builtin_strcmp’ makes
pointer from integer without a cast
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: passing argument 1 of ‘__builtin_strcmp’ makes
pointer from integer without a cast
client.c:207: warning: cast to pointer from integer of different size
client.c:207: warning: passing argument 1 of ‘__builtin_strcmp’ makes
pointer from integer without a cast
client.c:221: warning: assignment makes pointer from integer without a cast
client.c: In function ‘client_handle_untagged’:
client.c:278: warning: passing argument 1 of ‘t_str_ucase’ makes pointer
from integer without a cast
client.c:286: warning: passing argument 1 of ‘t_str_ucase’ makes pointer
from integer without a cast
client.c:312: warning: pointer/integer type mismatch in conditional
expression
client.c: In function ‘client_input_args’:
client.c:354: warning: assignment makes pointer from integer without a cast
client.c:378: warning: assignment makes pointer from integer without a cast
make[2]: *** [client.o] Error 1
make[2]: Leaving directory /root/imaptest-20100221/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory
/root/imaptest-20100221'
make: *** [all] Error 2
-- Best regards, Proskurin Kirill
On Wed, 2010-04-07 at 14:31 +0400, Proskurin Kirill wrote:
I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation
But get this: ./configure --with-dovecot=../dovecot-2.0.beta4 && make
Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future..
On 04/07/2010 03:39 PM, Timo Sirainen wrote:
On Wed, 2010-04-07 at 14:31 +0400, Proskurin Kirill wrote:
I try to build Imaptest and follow http://www.imapwiki.org/ImapTest/Installation
But get this: ./configure --with-dovecot=../dovecot-2.0.beta4&& make
Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future..
Thx!
But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0
-- Best regards, Proskurin Kirill
On Wed, 2010-04-07 at 16:08 +0400, Proskurin Kirill wrote:
Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future..
Thx!
But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0
Well, I'm rather thinking that the code needs fixing, not wiki. :)
On 04/07/2010 04:24 PM, Timo Sirainen wrote:
On Wed, 2010-04-07 at 16:08 +0400, Proskurin Kirill wrote:
Yeah, imaptest currently builds only against v1.2 code. I'll update it to compile with v2.0 sometimes in future..
Thx!
But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0
Well, I'm rather thinking that the code needs fixing, not wiki. :)
Yes, but code update may be not soon but wiki update is few seconds and fix an misunderstanding. ;-)
Anyway - could you give some examples of using ImapTest for testing\benchmarking?
Yes I saw http://www.imapwiki.org/ImapTest/Examples but I not a programmer and I don`t know IMAP protocol well and this numbers give me near nothing.
If you have some time - it will be nice to make some examples for admins. Especially I(and I think many others) interested in stress testing and benchmarking. Ideal it will be something like a Postfix "smtp-source".
It is just a friendly "feature request".
-- Best regards, Proskurin Kirill
On Wed, 2010-04-07 at 17:10 +0400, Proskurin Kirill wrote:
But seems to wiki needs fixing then. Because http://dovecot.org/nightly/dovecot-latest.tar.gz is 2.0
Well, I'm rather thinking that the code needs fixing, not wiki. :)
Yes, but code update may be not soon but wiki update is few seconds and fix an misunderstanding. ;-)
The wiki would then have to be updated back. I anyway updated imaptest now.
Anyway - could you give some examples of using ImapTest for testing\benchmarking?
Yes I saw http://www.imapwiki.org/ImapTest/Examples but I not a programmer and I don`t know IMAP protocol well and this numbers give me near nothing.
There isn't really much else it can give you.. imaptest isn't useful for testing real world performance. The numbers it gives are mostly useful only when compared against another setup with the same imaptest parameters. The one exception I can think of is how many msgs/second you can save to a mailbox:
imaptest - append=100 clients=10
participants (2)
-
Proskurin Kirill
-
Timo Sirainen