mcheck and check are not the same thing, don't build with --enable-debug and pidgin should stop looking for mcheck (it has been removed from pidgin for the next release anyway because it wasn't doing what we wanted anyway). Plus, --enable-debug has never really done anything of much use at any time in pidgin anyway.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear all:
Current Pidgin tarball requires check (http://sourceforge.net/projects/check/).
I don't have root access and I couldn't get check installed.
Is there anyway to compile pidgin without this check package? e.g. tweak with configure flag or something?
thanks
Harv
pidgin should build just fine without check, is looking for that causing your configure to fail?
"configure" went through without incident.
It is when I tried to compile it, it complains:
gmake[5]: Entering directory `/home/hk152093/tmp/install/pidgin-2.0.0/libpurple/plugins'
/bin/bash ../../libtool --silent --tag=CC --mode=link gcc -g -g -O2 -o autoaccept.la -rpath /home/hk152093/lib/purple-2 -module -avoid-version autoaccept.lo -L/home/hk152093/lib -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lpthread -lthread -lrt -lglib-2.0 -lsocket -lnsl -lresolv -lmcheck
ld: fatal: library -lmcheck: not found
ld: fatal: File processing errors. No output written to .libs/autoaccept.so
collect2: ld returned 1 exit status
mcheck and check are not the same thing, don't build with --enable-debug and pidgin should stop looking for mcheck (it has been removed from pidgin for the next release anyway because it wasn't doing what we wanted anyway). Plus, --enable-debug has never really done anything of much use at any time in pidgin anyway.
Thanks. It went through, eventhough I am still trying to get it to run on my machine.
I've noticed that a lot of work has been put into this tarball compare with the beta version.
Thank you.
Harv