aMule Forum
English => Compilation problems => Topic started by: OldFrog on July 01, 2008, 08:02:19 AM
-
Hi, I'm compiling everyday(s snapshotand now I have this issue
"checking for libupnp version >= 1.6.6... no (version 1.6.3 is not new enough)"
I am on Mandriva 2008.1 (Spring) and I try to create my RPMS for aMule from vanilla. Do we really need this higher version of upnp ?
I'd prefer not to create an RPM for upnp too.
-
I have the same problem with Ubuntu 8.04 32bit.
schutti@hell:~/Desktop/X/aMule/amule-cvs$ ./configure --disable-debug --enable-optimize
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking if this is a FreeBSD 4 or earlier system... no
checking for g++... g++
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 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) mawk
checking for egrep... grep -E
checking whether make sets $(MAKE)... (cached) yes
checking for flex... flex
checking for yywrap in -lfl... yes
checking lex output file root... lex.yy
checking whether yytext is a pointer... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for bison... bison -y
checking for ranlib... (cached) ranlib
checking for strip... strip
checking for ar... ar
checking for ld... ld
checking for zlib >= 1.1.4... yes (version 1.2.3.3)
checking for File::Copy... ok
checking whether we need the GUI... yes
checking for the --with-toolkit option... will be automatically detected
checking for the --with-wxshared option... will be automatically detected
checking for the --with-wxdebug option... will be automatically detected
checking for the --with-wxversion option... will be automatically detected
checking for wx-config... /usr/bin/wx-config
checking for wxWidgets version >= 2.8.0 (--unicode=yes)... yes (version 2.8.7)
checking for wxWidgets static library... no
checking if wxWidgets was built in DEBUG mode... no
checking if wxWidgets was built in STATIC mode... no
checking which wxWidgets toolkit was selected... gtk2
checking for libupnp presence... --prefix: unknown option
yes (installed in the system)
checking for libupnp version >= 1.6.6... no (version 1.4.3 is not new enough)
configure: error: Unable to find libupnp.
schutti@hell:~/Desktop/X/aMule/amule-cvs$
-
Schuttwegraeumer
libupnp 1.6.6 deb package: http://packages.ubuntu.com/intrepid/libupnp3
-
I was trying to compile libupnp myself, and after doing so, i always get the error that says not being able to find libupnp.so.3 ......
i compiled libupnp like this:
.configure
make
sudo make install
I know this is not libupnp forum, hehe, but ¿Is there anything i do wrong when compiling it?
The deb package, meanwhile, looks to work properly, anyway..
Cheers!
-
Schuttwegraeumer
libupnp 1.6.6 deb package: http://packages.ubuntu.com/intrepid/libupnp3
Ok, at the moment there is libupnp2 and libupnp-dev installed on my system.
Should I replace thes two packages with this .deb?
Its a version for 8.10, I have 8.04.
-
No package 'libupnp' found
yes (installed in the system)
checking for libupnp version >= 1.6.6... no (version is not new enough)
configure: error: Unable to find libupnp.
Do I need the libupnp3-dev too?
In the list of needet packages for compiling amule there was the libupnp-dev and the non dev version will be install becaus of the dependencies.
EDIT: http://packages.ubuntu.com/intrepid/libupnp-dev
-
Compile the aMule only need libupnp (libupnp2 or libupnp3) library installed. But remember that if you're not going to use UPnP support not need to compile the aMule with this option.
Uninstall libupnp2 and libupnp-dev
-
The libupnp-dev was in the needet libs list that must be installed to compile the aMule.
Now with the 1.6.6 libupnp-dev from the intribex REpo the configure worked well:
wxWidgets 2.8.7 (gtk2,shared)
crypto++ 5.5.2 (installed, in /usr)
libupnp 1.6.6 (system, in )
libintl system
zlib 1.2.3.3
-
Well, try to use only libupnp3 and see if works
-
Well, try to use only libupnp3 and see if works
I asked because it dont worked with the libupnp3 only.
With the libupnp-dev 1.6.6 from the same repostiory for Ibex it works.
See
http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian#What_developement_packages
-
OK, I oculd find a src rpm for Cooker and adapted it to Mandriva 2008.1
Here your stuff
http://www.oldfrog.info/Linux/RPMs/
For other architecture on Mandriva (x64, ppc, etc) please do a rpm --rebuild libupnp-1.6.6-1mdv2008.1.src.rpm
That should do the trick.
-
Hi, with and without libupnp 1.6.6 installed I get same error with this configuration:
./configure --prefix=/usr \
--disable-ccache \
--disable-debug \
--enable-optimize \
--disable-profile \
--disable-monolithic \
--enable-amule-daemon \
--enable-amulecmd \
--enable-webserver \
--disable-amule-gui \
--enable-cas \
--disable-wxcas \
--disable-alc \
--enable-alcc \
--disable-upnp \
--enable-geoip \
--disable-rpath \
--enable-nls
make
The summary of configure command and error messages from make are here:
http://pastebin.com/m4325b199
I don't understand why is compiling upnp if I explicitly said: --disable-upnp.
Anyway, if you need more information or I can do something to avoid the problem, please, let me know. TIA.
-
The question is, why is such a new version needed. This version is such a new one, that it is just 9 day in debian sid. For stable (and testing for today and maybe longer, depending on the appearing bugs) backports are needed. Is such a bleeding version really needed?
-
The question is, why is such a new version needed. This version is such a new one, that it is just 9 day in debian sid. For stable (and testing for today and maybe longer, depending on the appearing bugs) backports are needed. Is such a bleeding version really needed?
Sorry, I don't get you. What version are you talking about?
If libupnp -> I don't use it (as you can see looking at configure options), I was testing if problem is gone after install it.
If amule-SVN -> I like the wild side of life ;D
By the way, I'm using Arch Linux not Debian.
-
As I do daily svn-builds, I think I'm talking about libupnp. Is there anything really needed that is just in this new version aviable?
-
As I do daily svn-builds, I think I'm talking about libupnp. Is there anything really needed that is just in this new version aviable?
That was my big question as well this early morning ;D
-
Not to me, I don't even configure it (IIRC: --disable-upnp).
The ports of my router are assigned only by me. :D
-
That was my big question as well this early morning ;D
Unfortunately not. For testing I have hopes that libupnp arrives this night, for stable I have to backport.
-
Reporting to all who has the doubt:
I just checked it: both
http://packages.ubuntu.com/intrepid/libupnp-dev
and
http://packages.ubuntu.com/intrepid/libupnp3
Are needed for compiling aMule with UPnP feature enabled.
-
Indeed they are.
And yes, 1.6.6 is required.
-
and what about osx users?
-
What about them? It should work just as it works with wx or other libraries.
-
Since 1.6.6 my aMule is much slower than with lower versions.
-
...
You have no idea what you're talking about, do you?
-
I mean since the libupnp 1.6.6 is aMule on my PC much slower than before.
That should no be a problem on modern PCs but on a older PC aMule is very slow now. >:(
-
That's unrelated to uPnP. Right now aMule in svn takes way too many resources, yes, but that will be fixed.
-
As a temporary workaround you can turn off the progress bars. ;D
-
For debian stable I've made the needed backports.
-
For all those who asked, libupnp 1.6.6 is needed because every other version before that has bugs. We need no bugs around, do we? If your distro has not updated it, please ask them to, there is no reason not to do it.
As a temporary workaround, amule tarball includes a script called "amule_build_install.sh" that shows exactly what you need to do if you decide to compile anything by hand.
Cheers!
-
At least for debian stable there is a reason to not update this. The release policy. For other distros I don't know.
-
I compiled libupnp by hand like this:
First, i downloaded the tar.bz2 from sourceforge
http://mesh.dl.sourceforge.net/sourceforge/pupnp/libupnp-1.6.6.tar.bz2
After uncompressing it, i did this:
./configure --enable-debug
make
sudo make install
Then i compiled amule:
./configure --prefix=/usr --enable-amule-gui --enable-alc --enable-alcc --enable-utf8-systray --enable-debug --disable-optimize --enable-amulecmd --enable-monolithic --enable-amule-daemon --enable-cas --enable-wxcas --enable-webserver --enable-ccache --enable-geoip --enable-remote
No errors, and upnp flag detected in the report
make
sudo make install
All went fine, like allways, but when i launch amule
amule
i get this error:
amule: error while loading shared libraries: libupnp.so.3: cannot open shared object file: No such file or directory
So i did this:
jon@Hardy:~$ locate libupnp.so.3
/home/jon/libupnp-1.6.6/upnp/.libs/libupnp.so.3
/home/jon/libupnp-1.6.6/upnp/.libs/libupnp.so.3.0.5
/home/jon/libupnp-1.6.6/upnp/.libs/libupnp.so.3.0.5T
/usr/local/lib/libupnp.so.3
/usr/local/lib/libupnp.so.3.0.5
And, obviously, amule does not run at all.. :(
The machine is Ubuntu Server 8.04
I need to compile upnp by hand because i want to test it and report some backtraces, because i found some problems with it...
How can i fix this problem??
Thanks!
-
Try to start aMule as follows:
LD_LIBRARY_PATH=/home/jon/libupnp-1.6.6/upnp/.libs/ amule
I believe neither /usr/local/lib nor the path in your home directory are default search paths (see /etc/ld.so.conf to check this), so it won't search for the library there. Google LD_LIBRARY_PATH and /etc/ld.so.conf for more information.
Edit: it's lib, not bin...
-
And why amule does not try to search the library in /usr/local/lib/libupnp.so.3 , which would be the logic action?
thanks!
-
aMule doesn't search, the operating system does. As I said above, I believe /usr/local/bin is not in /etc/ld.so.conf and will therefore not be searched.
-
Try to start aMule as follows: LD_LIBRARY_PATH=/home/jon/libupnp-1.6.6/upnp/.libs/ amule
Thanks wuischke, this worked perfectly ;)
-
And why amule does not try to search the library in /usr/local/lib/libupnp.so.3 , which would be the logic action?
You may want to add /usr/local/lib to /etc/ld.so.conf and run ldconfig as root. It is usually a good idea to run ldconfig after installing a shared library.
-
You may want to add /usr/local/lib to /etc/ld.so.conf and run ldconfig as root. It is usually a good idea to run ldconfig after installing a shared library.
This worked perfectly.
thanks!!
-
The only thing I have to add is that in your case, the correct path to add to ld.so.conf is /usr/local/lib/, which btw, in most distributions should already be there, and is where "make install" has placed the library files. The path /home/jon/libupnp-1.6.6/upnp/.libs/ is the place where you have compiled and created the library originally. If you for some reason delete the source files directory, your library will be lost. Not to mention that other users in your system will not have access to the library if it remains there.
Cheers!
-
The only thing I have to add is that in your case, the correct path to add to ld.so.conf is /usr/local/lib/, which btw, in most distributions should already be there, and is where "make install" has placed the library files. The path /home/jon/libupnp-1.6.6/upnp/.libs/ is the place where you have compiled and created the library originally. If you for some reason delete the source files directory, your library will be lost. Not to mention that other users in your system will not have access to the library if it remains there.
Cheers!
Thnaks phonenix, i already actually did it the way u said.....
Thanks again