Difference between revisions of "Talk:HowTo Compile In Debian/Ubuntu"
Line 12: | Line 12: | ||
28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;) | 28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;) | ||
+ | |||
+ | other info : In my Sarge, with libcrypto++5.1_5.1-5_i386.deb and libcrypto++-dev_5.1-5_i386.deb package, I have an error : ld cannot find lcryptopp.. | ||
+ | |||
+ | so, I have made a link with this command : "ln -s /usr/lib/libcrypto++5.1.so /usr/lib/libcryptopp.so" and run ldconfig -> it work ! |
Revision as of 18:49, 28 September 2004
To successully compile aMule in my Sarge I had to create a link like this:
ln -s /usr/include/crypto++ /usr/include/cryptopp
because the make process searchs for config.h in cryptopp directory, not in crypto++.
They might have hanged th pathnames again. Thanks for the info :-)
The problem is that both crypto++ and Debian's crypto++ package have been changing the pathnames in order to suit, and this has become a mess. hehehe
Anyway, since next aMule release (it is currenly already implemented into aMule CVS) crypto++ will no longer be needed since it's necessary functions have been coded into aMule.
Again, thanks for the info!
28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;)
other info : In my Sarge, with libcrypto++5.1_5.1-5_i386.deb and libcrypto++-dev_5.1-5_i386.deb package, I have an error : ld cannot find lcryptopp..
so, I have made a link with this command : "ln -s /usr/lib/libcrypto++5.1.so /usr/lib/libcryptopp.so" and run ldconfig -> it work !