aMule Forum

English => Compilation problems => Topic started by: x_x_kamikaze_x_x on April 14, 2012, 06:25:14 PM

Title: Error compiling aMule SVN:10778
Post by: x_x_kamikaze_x_x on April 14, 2012, 06:25:14 PM
Hi aMule Team!

More and more problems!  :D

Command used to configure the aMule code:
Code: [Select]
./configure --enable-optimize --enable-cas --enable-wxcas --enable-alc --enable-alcc --enable-xas --enable-geoip --enable-mmap --enable-fileview --with-zlib --enable-ccache --enable-debug --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon --with-boost=./boost_1_49_0/
Final output:
Code: [Select]
  Configure script has finished system check.

  Configured aMule SVN (rev. 10778) for 'x86_64-unknown-linux-gnu'.

  aMule enabled options:

  **** aMule Core ****
  Prefix where aMule should be installed?                    /usr/local
  Should aMule be compiled with i18n support?                yes
  Should aMule be compiled in debug mode?                    yes
  Should aMule be compiled with profiling?                   no
  Should aMule be compiled with optimizations?               yes
  Should aMule be compiled with UPnP support?                yes
  Should aMule be compiled with IP2country support?          yes
  Should aMule monolithic application be built?              no
  Should aMule daemon version be built?                      yes
  Should aMule remote gui be built?                          no
  Crypto++ library/headers style?                            installed

  **** aMule TextClient ****
  Should aMule Command Line Client be built?                 yes

  **** aMule WebServer ****
  Should aMule WebServer be built?                           yes

  **** aMule ED2K Links Handler ****
  Should aMule ED2K Links Handler be built?                  yes

  **** aMuleLinkCreator ****
  Should aMuleLinkCreator GUI version (alc) be built?        yes
  Should aMuleLinkCreator for console (alcc) be built?       yes

  **** aMule Statistics ****
  Should C aMule Statistics (CAS) be built?                  yes
  Should aMule GUI Statistics (wxCas) be built?              yes
  Should xas XChat2 plugin be installed?                     yes
  Should plasmaMule plasma-applet be build?                  no

  **** General Libraries and Tools ****
  Should ccache support be enabled?                          yes
  Libraries aMule will use to build:
                             wxWidgets             2.8.12 (gtk2,shared)
                             boost                 1.49 (in ./boost_1_49_0/)
                             crypto++              5.6.1 (installed, in /usr)
                             libupnp               1.6.6
                             libintl               system
                             libpng                1.2.46
                             libgd                 2.0.36
                             zlib                  1.2.3.4

Problem when making...
Code: [Select]
make[3]: Entering directory `/home/kami/Desktop/aMule SVN/src'
/usr/bin/ccache g++ -DHAVE_CONFIG_H -I. -I..  -D__DEBUG__ -DUSE_WX_EXTENSIONS -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -DwxUSE_GUI=0 -I./boost_1_49_0/ -I./libs -I./include  -g -W -Wall -Wshadow -Wundef -ggdb -fno-inline -fmessage-length=0 -O2  -MT libmulesocket_a-LibSocket.o -MD -MP -MF .deps/libmulesocket_a-LibSocket.Tpo -c -o libmulesocket_a-LibSocket.o `test -f 'LibSocket.cpp' || echo './'`LibSocket.cpp
In file included from LibSocket.cpp:31:0:
LibSocketAsio.cpp:54:52: fatal error: boost/../libs/system/src/error_code.cpp: No such file or directory
compilation terminated.
make[3]: *** [libmulesocket_a-LibSocket.o] Error 1
make[3]: Leaving directory `/home/kami/Desktop/aMule SVN/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/kami/Desktop/aMule SVN/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/kami/Desktop/aMule SVN'
make: *** [all] Error 2

I think it's using the dir: /home/kami/Desktop/aMule SVN/boost_1_49_0/
as the base, so when it go down using "../libs/system/src/error_code.cpp"
he is on /home/kami/Desktop/aMule SVN/, so the dir ./libs/ don't exist...

I hope the post of this issue it's useful to improve the compilation of the software!  ;D

See you soon!  :)
Title: Re: Error compiling aMule SVN:10778
Post by: Stu Redman on April 14, 2012, 07:08:50 PM
You have to give an absolute path (like /home/kami/Desktop/boost_1_49_0 ) to --with-boost .
Title: Re: Error compiling aMule SVN:10778
Post by: x_x_kamikaze_x_x on April 14, 2012, 08:37:47 PM
Hi Stu Redman!   :)

The problem is that if I use a absolute path the ./configure break with a "./configure: line 17534: test: too many arguments"....

Command:
Code: [Select]
kami@maria2:~/Desktop/aMule SVN$ ./configure --enable-optimize --enable-cas --enable-wxcas --enable-alc --enable-alcc --enable-xas --enable-geoip --enable-mmap --enable-fileview --with-zlib --enable-ccache --enable-debug --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon --with-boost="/home/kami/Desktop/aMule SVN/boost_1_49_0/"

Result:
Code: [Select]
  Configure script has finished system check.

  Configured aMule SVN (rev. 10778) for 'x86_64-unknown-linux-gnu'.

  aMule enabled options:

  **** aMule Core ****
  Prefix where aMule should be installed?                    /usr/local
  Should aMule be compiled with i18n support?                yes
  Should aMule be compiled in debug mode?                    yes
  Should aMule be compiled with profiling?                   no
  Should aMule be compiled with optimizations?               yes
  Should aMule be compiled with UPnP support?                yes
  Should aMule be compiled with IP2country support?          yes
  Should aMule monolithic application be built?              no
  Should aMule daemon version be built?                      yes
  Should aMule remote gui be built?                          no
  Crypto++ library/headers style?                            installed

  **** aMule TextClient ****
  Should aMule Command Line Client be built?                 yes

  **** aMule WebServer ****
  Should aMule WebServer be built?                           yes

  **** aMule ED2K Links Handler ****
  Should aMule ED2K Links Handler be built?                  yes

  **** aMuleLinkCreator ****
  Should aMuleLinkCreator GUI version (alc) be built?        yes
  Should aMuleLinkCreator for console (alcc) be built?       yes

  **** aMule Statistics ****
  Should C aMule Statistics (CAS) be built?                  yes
  Should aMule GUI Statistics (wxCas) be built?              yes
  Should xas XChat2 plugin be installed?                     yes
  Should plasmaMule plasma-applet be build?                  no

  **** General Libraries and Tools ****
  Should ccache support be enabled?                          yes
  Libraries aMule will use to build:
                             wxWidgets             2.8.12 (gtk2,shared)
./configure: line 17534: test: too many arguments
                             crypto++              5.6.1 (installed, in /usr)
                             libupnp               1.6.6
                             libintl               system
                             libpng                1.2.46
                             libgd                 2.0.36
                             zlib                  1.2.3.4

So I used a relative path to fix it...  and then it breaks again!   ;D

Title: Re: Error compiling aMule SVN:10778
Post by: Stu Redman on April 15, 2012, 04:14:42 PM
Well, blanks in directory names ought to be forbidden.  ::)
I'm sure there's some way to get this running like it is, but easiest would be to just rename it and remove the blank.
Title: Re: Error compiling aMule SVN:10778
Post by: x_x_kamikaze_x_x on April 15, 2012, 04:50:39 PM
Well, blanks in directory names ought to be forbidden.  ::)
Mmm...  and why they implemented the escape chars like ' \ '?  ;)

I'm sure there's some way to get this running like it is, but easiest would be to just rename it and remove the blank.

You are right, I have renamed the dir and all it's working fine now!  ;D

Thanks again Stu Redman and see you soon!  :)