Difference between revisions of "Talk:HowTo Compile In Debian/Ubuntu"
From AMule Project FAQ
(Debian Sarge aMule compilation: crypto++ link needed) |
|||
| Line 1: | Line 1: | ||
To successully compile aMule in my Sarge I had to create a link like this: | 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 :-)<br> | ||
| + | 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<br> | ||
| + | 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.<br> | ||
| + | Again, thanks for the info!''' | ||
Revision as of 02:44, 9 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!
