Hm, is it true that you run debian? Why are you going to gtk.org to download the tarball? If you are going to install the tarball, you'll need to compile it, an thus you'll need the development packages of XFree. That's the reason of the message: "X libraries or include files not found"

Some basics on linux software: Usually developers split whatever they write into two files: a header and a c/c++ file. Compiling uses both files to make an object file. These object files are linked to make a programm you can run. Now a pre-compiled package is basically the programm and some additional stuff.

However, some programms are linked against other packages when compiled. To be able to link against these packages you need the header files. These header files are in the development packages. That's why you often have two or more packages out of one tarball: a programm and a development package (the gtk tarball is coming in five packages under debian, for example)!

Getting these development packages is a really easy thing; no need to install and compile tarballs. In fact, chances are you can bring your system into an unusable state if you have no plan what to do.

Then central question is now: What Debian distribution are you using (Sorry. I haven't seen it before.)?

If you're using sarge (testing) or sid (unstable), imply use: and there you go! If you're using woody, you'll need a backport. Add the following lines to your "/etc/apt/sources.list":
Then, use "apt-get update" as root to update your package information and then use the above command to install xMule.

Everything is just simple under Debian.

Note: Only install tarballs if there's absolutly no other way. Best way under woody is to use a backport, if there's none, you can make yourself one (this is also rather simple). If you have no backport or no sources in testing or unstable to make yourself one, then there is the "checkinstall" way to make a debian package out of tarballs!

Thanks for your reply seneca! Yes, your absolutely right, I am indeed using debian (3.0 stable).
A few minutes ago I had a friend of mine come over and he told me almost exactly what you did now.

Result: Works perfectly

thanks a lot!
TCRK

I'm using Mandrake 9.1....

I have wx-windows and GTK installed, and I can run ./configure without a problem, but when I do 'make' i get the following:

[barend@localhost xmule-1.6.0]$ make
make all-recursive
make[1]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0'
Making all in intl
make[2]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/intl'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/intl'
Making all in m4
make[2]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/m4'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/m4'
Making all in src
make[2]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/src'
Making all in wx
make[3]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/src/wx'
Making all in xrc
make[4]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/src/wx/xrc'
make[4]: Nothing to be done for `all'.
make[4]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/src/wx/xrc'
make[4]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/src/wx'
make[4]: Nothing to be done for `all-am'.
make[4]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/src/wx'
make[3]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/src/wx'
make[3]: Entering directory `/home/barend/Documents/Downloads/xmule-1.6.0/src'
source='AddFriend.cpp' object='AddFriend.o' libtool=no \
depfile='.deps/AddFriend.Po' tmpdepfile='.deps/AddFriend.TPo' \
depmode=gcc3 /bin/sh ../depcomp \
g++ -DHAVE_CONFIG_H -D__GSOCKET_STANDALONE__ -I. -I. -I.. -g -I/usr/local/lib/wx/include/x11univ-2.4 -D__WXUNIVERSAL__ -D__WXX11__ -I/usr/X11R6/include -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-1.2 -I/usr/include/glib-1.2 -I/usr/lib/glib/include -I/usr/X11R6/include -Isrc -c -o AddFriend.o `test -f 'AddFriend.cpp' || echo './'`AddFriend.cpp
In file included from CMuleNotebookBase.h:279,
from SearchDlg.h:34,
from xmuleDlg.h:33,
from xmule.h:30,
from AddFriend.cpp:23:
MuleNotebook.h:118: `GdkWindow' was not declared in this scope
MuleNotebook.h:118: `window' was not declared in this scope
MuleNotebook.h:118: invalid data member initialization
MuleNotebook.h:118: (use `=' to initialize static data members)
make[3]: *** [AddFriend.o] Error 1
make[3]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/barend/Documents/Downloads/xmule-1.6.0'
make: *** [all] Error 2

Any ideas of what this might mean?

Seneca you are the king of the newbies Thank you very much
The installation of xmule on my SuSE 9.0 takes me 3 days lol
Here is the whole story...

First I downloaded the 1.6.1 tar.gz from a mirror site in Belgium. I don't know what happened but as a newbie I didn't noticed that the extraction give me only m4 and po directories in xmule 1.6.1 lol of course I tried to compile with it rofl
Perhaps I have closed the konqueror window before the end of download Mystery...
In the meanwhile the ./configure script give me
checking for GTK version....
*can't find GTK 1.2 blablabla....*
But GTK was here from the beginning
I've made my investigation.I try several things like adding cross-compiling='yes' in configure file don't know why but i see a line in configure.log printing this. It made the error with GTK to disapear don't know why but the "make" don't execute to the end and delivered an fatal error lol

I have installed some developpement packages which needed to be linked. I follow the INSTALL txt
But the problem remains.So I come here and when I see your post It makes tilt
Yessssss I forget the XFree86 developpement packages
So I install them with also the full 1.6.1 tar.gz package this time
And the compilation went to the end and successed

Now I want to understand why ./configure is complaining so much about GTK and not enough about XFree86-devel
Where is the checking of this in configure?
Or is this stage so evident that it isn't mentioned?

Best Regards

Thanks, but this is too much honor. It was just a good guess.

I don't understand the issues completely yet so the following explanation is somewhat limited probably.

When you look at some file the source code directory xmule-1.6.1/src, you can see at the beginning of some files stuff like . This lines tell the precompiler (I think) to replace the line with the original text file /usr/lib/<add_dirs>/wx/panel.h

Somewhere in the xmule code is also something for GTK, and GTK might also come in via wxWindows. And since GTK needs X you'll also need the xlibs dev files (the headers from XFree).

If all configure scripts check for all dependencies down to the very first level, they would be rather long. Thus, they are written to just check the basic dependencies - that is, the existence of the most needed header files. Another reason might be the following: If you compile yourself, you would have already compiled the dependencies yourself. Their configure scripts would have already checked the existence of their dependencies.

Put simply: If you're compiling xMule, you'll should have wxWindows compiled which should have checked for GTK. Then you should have compiled GTK which should have checked for xLibs. xLibs, once again, should have checked for their dependencies and so on.

If you're using a distribution with a good package management, these "dependencies" will be solved automatically. For example, debian's apt-get installs also xlib development files if you install gtk development files.

Maybe this is not a perfect explanation but it might help you and others.