Hi!
I just wrote this little guide to help you all solaris fans. Hope this helps!
COMPILING AMULE/AMULEWEB ON SOLARIS 10 x86
[list=1]
- Install the pkg-get script from http://www.blastwave.org/pkg-get.php
- Use the pkg-get script to install some required libraries, which do not come with solaris:
autoconf
automake
gd
gettext
gtk/gtk2
libpng
binutils
These packages will install to /opt/csw tree
PATH=/usr/local/bin:/opt/csw/bin:/usr/sfw/bin:/usr/bin
- Simlink the GNU utilities in /usr/sfw/bin (or the ones in /opt/csw/bin) to their "right" names (gar=ar, gas=as, gld=ld, gmake=make, ggrep=grep,
gtar=tar, gsed=sed, gautopoint=autopoint, gbc=bc, etc...) somewhere in your path. I simlinked them to their same directory.
- Now, get the latest wxGTK package from http://www.wxwidgets.org and compile it. Install it to /usr/local. I have not
tried compiling it with unicode support, nor against GTK2, so basically this is untested. But should work.
- Get the latest amule CVS from http://amule.hirnriss.net and uncompress it somewhere.
- Set these two environment wariables:
CPPFLAGS='-I /opt/csw/include'
LDFLAGS='-L/usr/local/lib:/opt/csw/lib:/usr/sfw/lib:/usr/openwin/lib:/usr/dt/lib:/usr/lib:/lib -R/usr/local/lib:/opt/csw/lib:/usr/lib:/usr/sfw/lib:/lib:/usr/dt/lib:/usr/openwin/lib'
- Configure amule like this:
./configure --enable-webserver
- Type "make" (without the quotation marks), press and hope for the best.
- If compilation went OK, you can now run amule!
./src/amule
COMPILING AMULE/AMULEWEB ON SOLARIS 11 x86
[list=2]
- Install the pkg-get script from http://www.blastwave.org/pkg-get.php
- Use the pkg-get script to install some required libraries, which do not come with solaris, or the included ones will not work for some reason I don't know:
autoconf
automake
gd
gettext
gtk/gtk2
libpng
binutils
gmake
gcc3
These packages will install to /opt/csw tree
PATH=/usr/local/bin:/opt/csw/gcc3/bin:/opt/csw/bin:/usr/sfw/bin:/usr/bin
- Simlink the GNU utilities in /opt/csw/bin to their "right" names (gar=ar, gas=as, gld=ld, gmake=make, ggrep=grep,
gtar=tar, gsed=sed, gautopoint=autopoint, gbc=bc, etc...) somewhere in your path. I simlinked them to their same directory.
- Now, get the latest wxGTK package from http://www.wxwidgets.org and compile it. Install it to /usr/local. I installed it using GTK2, but forgot to add the unicode support :(. This will be tested later. It compiled fine using GTK2.
- Get the latest cryptopp library from http://www.cryptopp.com and install it somewhere on your system (I know aMule includes a bundled cryptopp libraries, but when compiling on solaris, they refused to create my keys for secureID, so Kry suggested installing external cryptopp, which worked fine). For installing it, create somewhere a folder named cryptopp (for example: /temp/crypto521), move the zip file to that cryptopp foldeer you just created and unzip it. Then you simply run make and hope for the best. I will assume you uncompressed the .zip into /temp/crypto521.
- Get the latest amule CVS from http://amule.hirnriss.net and uncompress it somewhere.
- Set these two environment wariables:
CPPFLAGS='-I /opt/csw/include -I/temp/crypto521'
LDFLAGS='-L/usr/local/lib:/opt/csw/lib:/usr/sfw/lib:/usr/openwin/lib:/usr/dt/lib:/usr/lib:/lib -R/usr/local/lib:/opt/csw/lib:/usr/lib:/usr/sfw/lib:/lib:/usr/dt/lib:/usr/openwin/lib'
The CPPFLAGS are parameters send to the compiler, -I tells where to find the include files (the first -I is for gd,png and other includes you installed on the second step, the second -I is the folder where you created the cryptopp folder and installed cryptopp)
The LDFLAGS are parameters to the linker: -L tell where to find libraries in non-standard places during linking, -R tells where to find libraries in non-standard places at runtime.
- Configure amule like this:
./configure --enable-webserver --enable-amule-daemon --enable-amulecmd --enable-amule-gui --enable-cas --enable-wxcas --enable-alc --enable-alcc --enable-optimize --disable-debug --disable-embedded-crypto --with-crypto-prefix=/temp/cryptopp521/
- Type "make" (without the quotation marks), press and hope for the best.
- Most probably you will see lots of warnings, telling something about "The declaration is the place of previous declaration" or something like that. No idea why it happens (doesn't happen on linux) but the compilation finished OK. I think the includes in solaris have some problem, or maybe gcc doesn't use them right.
- If compilation went OK, you can now run amule!
./src/amule
- ENJOY!
[/list=2]
These guides were used for compiling amule and amuleweb on Solaris 10 FCS, and Solaris 11 b_24. I have no idea if they will work or not on
previous/later solaris releases, but they should. Also, if you got amule compiled on other solaris than 10 FCS or 11 b_24, please tell me how you did, or if this guide worked for you or any extra things you had to do, etc.
WRITTEN BY Skolnick on March 6/2005, modified on May 17, 19/2005. Solaris 11 part added on December 16th 2005.
Thanks goes to all the amule dev team, specially Kry, who helped me a lot, and ken for the CPPFLAGS tip also thanks to Gerd78 for the LDFLAGS tip.