aMule Forum
English => Compilation problems => Topic started by: smo on August 05, 2005, 07:26:27 PM
-
Hey everybody,
I try to use the guide in http://www.amule.org/wiki/index.php/HowTo_compile_on_Win32-de to compile amule (aMule-CVS-20050805.tar.bz2) for windows. The main reason is to test amulegui. Have I taken the right file for this?
Everything is ok until
13. ./configure --with-zlib=/home/(Benutzername)/aMule/zlibdll/ --disable-debug --enable-optimize --enable-static
It results in
$ ./configure --with-zlib=/home/me/aMule/zlibdll/ --enable-optimize --enable-static
checking build system type... i686-pc-mingw32
checking host system type... i686-pc-mingw32
checking target system type... i686-pc-mingw32
checking for a BSD-compatible install... /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 g++... g++
checking for C++ compiler default output file name... a.exe
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for gcc... gcc
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 dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for gawk... (cached) gawk
checking whether make sets $(MAKE)... (cached) yes
checking for a BSD-compatible install... /bin/install -c
checking for ranlib... ranlib
checking for bison... no
checking for byacc... no
checking whether ln -s works... yes
checking for ranlib... (cached) ranlib
checking for strip... strip
checking for ar... ar
checking for ld... ld
checking for egrep... 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 for zlib >= 1.1.4... no
configure: error: zlib >= 1.1.4 not found
So seems that zlib cannot be found. I don't know why:
me@DING ~/aMule/zlibdll
$ pwd
/home/me/aMule/zlibdll
$ ls
ChangeLog compress.c example.exe inflate.c msdos zconf.in.h
FAQ compress.o example.o inflate.h old zlib-1.2.3
INDEX configure examples inflate.o projects zlib.3
Makefile contrib gzio.c inftrees.c qnx zlib.h
Makefile.in crc32.c gzio.o inftrees.h trees.c ztest1984.exe
README crc32.h infback.c inftrees.o trees.h zutil.c
adler32.c crc32.o infback.o libz.a trees.o zutil.h
adler32.o deflate.c inffast.c make_vms.com uncompr.c zutil.o
algorithm.txt deflate.h inffast.h minigzip.c uncompr.o
amiga deflate.o inffast.o minigzip.exe win32
as400 example.c inffixed.h minigzip.o zconf.h
The wiki-page doesn't tell to compile zlib. Is this missing or really not necessary? However, I compiled zlib with configure, make, make install (no options). No erros occured, but the error remains the same.
Any hints?
smo
-
Try replacing "(Benutzername)" with your actual username.
-
Like shown in line 1 of the second code-paragraph, I did that. My windows-name is "me".
smo
-
XAignar has been pwned :P
Read the english version of the page. it's up-to-date and shows what to do with zlib ;)
-
Thanks, compilation finished without errors. :)
By the way, I updated the german "HowTo_compile_on_Win32"-page:
[http://www.amule.org/wiki/index.php/HowTo_compile_on_Win32-de]
smo
-
Ok, next question. ;)
Why is the "User name" in amulegui client hardcoded "amule"?
smo
-
Because aMule does not have yet multiuser support, but aMulegui connect dialog was taken from the future, so it already has a "'username" field. Whenever we'll have true multiuser support, this field will be enabled too. At the moment it has no meaning at all. (The default text for the control could be anything of course, maybe an empty default value would fit your needs more)