aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: [1] 2 3 4

Author Topic: Compilation problem  (Read 21416 times)

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Compilation problem
« on: October 04, 2010, 06:43:25 PM »
Hi guys, I was trying to compile by myself aMule 2.2.6 on a Mac with 10.6.4. First of all I've to say that I am absolutely new to any kind of programming, I have only some few little basic skills with the shell. However I was able to complete almost all the operation when I faced these errors:

Code: [Select]
ECMuleSocket.cpp: In member function ‘virtual int CECMuleSocket::InternalGetLastError()’:
ECMuleSocket.cpp:136: error: ‘wxSOCKET_DUMMY’ was not declared in this scope
ECMuleSocket.cpp:115: warning: enumeration value ‘wxSOCKET_OPTERR’ not handled in switch
make[7]: *** [ECMuleSocket.o] Error 1
make[6]: *** [all] Error 2
make[5]: *** [all-recursive] Error 1
make[4]: *** [all] Error 2
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

I compiled with success both wxWidgets (ver. 2.9.1) and aMule (ver. 2.2.6) but make gives me these error. Any help?
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Compilation problem
« Reply #1 on: October 04, 2010, 09:05:24 PM »
2.2.6 does not compile with wx 2.9 . You have to take aMule SVN version for wx 2.9. Or 2.2.6 with wx 2.8 .
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

myth

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 38
  • Offline Offline
  • Posts: 570
Re: Compilation problem
« Reply #2 on: October 04, 2010, 10:23:43 PM »
Take SVN ;) Much innovation in there!

Then...a better thread title wouldn't be bad!
Logged

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Re: Compilation problem
« Reply #3 on: October 05, 2010, 01:32:32 AM »
Quote from: Stu Redman on October 04, 2010, 09:05:24 PM
2.2.6 does not compile with wx 2.9 . You have to take aMule SVN version for wx 2.9. Or 2.2.6 with wx 2.8 .

Thanks for your rapid answers! I followed your instructions and I downloaded SVN 10306 published 5 days ago. But...a similar error occurred!
Here is the log:

Code: [Select]
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[5]: *** [wxcas] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Compilation problem
« Reply #4 on: October 05, 2010, 08:35:32 PM »
You left out the interesting part of the log.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Re: Compilation problem
« Reply #5 on: October 05, 2010, 09:03:31 PM »
Quote from: Stu Redman on October 05, 2010, 08:35:32 PM
You left out the interesting part of the log.

Do you really want ALL the make log? I read somewhere not to post the make log (in effect it say that the message is longer than 20.000 characters). Do you need a specific part?
Logged

GonoszTopi

  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 169
  • Offline Offline
  • Posts: 2685
Re: Compilation problem
« Reply #6 on: October 05, 2010, 10:06:55 PM »
Not all. The last screenful of the log (say, the last ~20 lines) should be more than enough. In your case, the 1-2 lines before what you posted hold critical information to solve your problem.
Logged
concordia cum veritate

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Re: Compilation problem
« Reply #7 on: October 05, 2010, 11:18:00 PM »
Quote from: GonoszTopi on October 05, 2010, 10:06:55 PM
Not all. The last screenful of the log (say, the last ~20 lines) should be more than enough. In your case, the 1-2 lines before what you posted hold critical information to solve your problem.

ok. Here it is:

Code: [Select]
wxSize const&, long, wxString const&)in wxcasprefs.o
  "wxWindowBase::GetHelpTextAtPoint(wxPoint const&, wxHelpEvent::Origin) const", referenced from:
      vtable for wxMDIParentFrameBasein onlinesig.o
      vtable for wxMDIClientWindowBasein onlinesig.o
      vtable for wxMDIParentFrameBasein linuxmon.o
      vtable for wxMDIClientWindowBasein linuxmon.o
      vtable for wxMDIParentFrameBasein wxcas.o
      vtable for wxMDIClientWindowBasein wxcas.o
      vtable for wxMDIParentFrameBasein wxcasprint.o
      vtable for wxMDIClientWindowBasein wxcasprint.o
      vtable for WxCasFramein wxcasframe.o
      vtable for wxMDIParentFrameBasein wxcasframe.o
      vtable for wxMDIClientWindowBasein wxcasframe.o
      vtable for wxStaticLineBasein wxcasframe.o
      vtable for WxCasPrefsin wxcasprefs.o
      vtable for wxMDIParentFrameBasein wxcasprefs.o
      vtable for wxMDIClientWindowBasein wxcasprefs.o
      vtable for wxCheckBoxBasein wxcasprefs.o
      vtable for wxStaticLineBasein wxcasprefs.o
      vtable for wxMDIParentFrameBasein wxcascte.o
      vtable for wxMDIClientWindowBasein wxcascte.o
      vtable for wxMDIParentFrameBasein wxcaspix.o
      vtable for wxMDIClientWindowBasein wxcaspix.o
  "vtable for wxTopLevelWindow", referenced from:
      wxTopLevelWindow::wxTopLevelWindow()in wxcasprefs.o
      wxTopLevelWindow::~wxTopLevelWindow()in wxcasprefs.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
make[5]: *** [wxcas] Error 1
make[4]: *** [all-recursive] Error 1
make[3]: *** [all-recursive] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Is it enough?
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: Compilation problem
« Reply #8 on: October 06, 2010, 10:19:14 PM »
Not really.

How did you configure wxWidgets? How did you configure aMule?
I think you may be missing the wxWidgets libs. But I really don't know much about Mac.
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Re: Compilation problem
« Reply #9 on: October 07, 2010, 01:00:00 AM »
Quote from: Stu Redman on October 06, 2010, 10:19:14 PM
Not really.

How did you configure wxWidgets? How did you configure aMule?
I think you may be missing the wxWidgets libs. But I really don't know much about Mac.

Ok then, let's start from the beginning.  Downloaded vxWidgets version 2.9.1 and configured it with
Code: [Select]
./configure --disable-shared --enable-unicode --disable-debug --disable-debug_gdb --with-libiconv-prefix=/opt/local/var/macports/software/libiconv/1.13.1_0/opt/local && make -j8 I post you some excepts of the log, when it print a WARNING, none explicit error detected.
Code: [Select]
checking for sw_vers... sw_vers
configure:18644: WARNING: gcc >= 4.2 cannot compile 10.4 compatible code. Using gcc 4.0 instead.

configure: WARNING: Defaulting to the builtin regex library for Unicode build.

checking for png.h > 0.90... no
checking for png.h... (cached) no
configure: WARNING: system png library not found or too old, will use built-in instead
checking for jpeglib.h... no
configure: WARNING: system jpeg library not found, will use built-in instead
checking for tiffio.h... no
configure: WARNING: system tiff library not found, will use built-in instead

checking for pthread_mutex_timedlock... no
configure: WARNING: wxMutex::LockTimeout() will not work

checking for sys/epoll.h... no
configure: WARNING: sys/epoll.h not available, wxEpollDispatcher disabled

checking for timezone variable in <time.h>... configure: WARNING: no timezone variable


config.status: WARNING:  Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/Makefile
config.status: WARNING:  contrib/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/acorn/Makefile
config.status: WARNING:  contrib/acorn/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/addtiffo/Makefile
config.status: WARNING:  contrib/addtiffo/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/dbs/Makefile
config.status: WARNING:  contrib/dbs/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/dbs/xtiff/Makefile
config.status: WARNING:  contrib/dbs/xtiff/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/iptcutil/Makefile
config.status: WARNING:  contrib/iptcutil/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/mac-cw/Makefile
config.status: WARNING:  contrib/mac-cw/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/mac-mpw/Makefile
config.status: WARNING:  contrib/mac-mpw/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/mfs/Makefile
config.status: WARNING:  contrib/mfs/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/ojpeg/Makefile
config.status: WARNING:  contrib/ojpeg/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/pds/Makefile
config.status: WARNING:  contrib/pds/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/ras/Makefile
config.status: WARNING:  contrib/ras/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/stream/Makefile
config.status: WARNING:  contrib/stream/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/tags/Makefile
config.status: WARNING:  contrib/tags/Makefile.in seems to ignore the --datarootdir setting
config.status: creating contrib/win_dib/Makefile
config.status: WARNING:  contrib/win_dib/Makefile.in seems to ignore the --datarootdir setting
config.status: creating html/Makefile
config.status: WARNING:  html/Makefile.in seems to ignore the --datarootdir setting
config.status: creating html/images/Makefile
config.status: WARNING:  html/images/Makefile.in seems to ignore the --datarootdir setting
config.status: creating html/man/Makefile
config.status: WARNING:  html/man/Makefile.in seems to ignore the --datarootdir setting
config.status: creating libtiff/Makefile
config.status: WARNING:  libtiff/Makefile.in seems to ignore the --datarootdir setting
config.status: creating man/Makefile
config.status: WARNING:  man/Makefile.in seems to ignore the --datarootdir setting
config.status: creating port/Makefile
config.status: WARNING:  port/Makefile.in seems to ignore the --datarootdir setting
config.status: creating test/Makefile
config.status: WARNING:  test/Makefile.in seems to ignore the --datarootdir setting
config.status: creating tools/Makefile
config.status: WARNING:  tools/Makefile.in seems to ignore the --datarootdir setting
Then aMule (SVN 10306). Here I have to edit the configure, in order to avoid it to check which version of the toolkit I am using. Here is the code modified:
Code: [Select]
if test "$TOOLKIT" = "auto" ; then

            #                        { echo "$as_me:$LINENO: checking which wxWidgets toolkit was selected" >&5
#echo $ECHO_N "checking which wxWidgets toolkit was selected... $ECHO_C" >&6; }
#
#            WX_GTKPORT1=$(expr "$WX_SELECTEDCONFIG" : ".*gtk1.*")
#            WX_GTKPORT2=$(expr "$WX_SELECTEDCONFIG" : ".*gtk2.*")
#            WX_MSWPORT=$(expr "$WX_SELECTEDCONFIG" : ".*msw.*")
#            WX_MOTIFPORT=$(expr "$WX_SELECTEDCONFIG" : ".*motif.*")
#            WX_MACPORT=$(expr "$WX_SELECTEDCONFIG" : ".*mac.*")
#            WX_X11PORT=$(expr "$WX_SELECTEDCONFIG" : ".*x11.*")
#            WX_MGLPORT=$(expr "$WX_SELECTEDCONFIG" : ".*mgl.*")
#            WX_DFBPORT=$(expr "$WX_SELECTEDCONFIG" : ".*dfb.*")
#
            WX_PORT="gtk2"
#            if test "$WX_GTKPORT1" != "0"; then WX_PORT="gtk1"; fi
#            if test "$WX_GTKPORT2" != "0"; then WX_PORT="gtk2"; fi
#            if test "$WX_MSWPORT" != "0"; then WX_PORT="msw"; fi
#            if test "$WX_MOTIFPORT" != "0"; then WX_PORT="motif"; fi
#            if test "$WX_MACPORT" != "0"; then WX_PORT="mac"; fi
#            if test "$WX_X11PORT" != "0"; then WX_PORT="x11"; fi
#            if test "$WX_MGLPORT" != "0"; then WX_PORT="mgl"; fi
#            if test "$WX_DFBPORT" != "0"; then WX_PORT="dfb"; fi
#
#
#            if test "$WX_PORT" = "unknown" ; then
#                { { echo "$as_me:$LINENO: error:
#        Cannot detect the currently installed wxWidgets port !
#        Please check your 'wx-config --cxxflags'...
#                            " >&5
#echo "$as_me: error:
#        Cannot detect the currently installed wxWidgets port !
#        Please check your 'wx-config --cxxflags'...
#                            " >&2;}
#   { (exit 1); exit 1; }; }
#            fi

            { echo "$as_me:$LINENO: result: $WX_PORT" >&5
echo "${ECHO_T}$WX_PORT" >&6; }
        else

                        if test -z "$TOOLKIT" ; then
                WX_PORT=$TOOLKIT
            else
                                WX_PORT=$PORT
            fi
        fiThen I can finally configure with:
Code: [Select]
./configure --with-wxdir=/Users/admin/Desktop/aMuleSVN/wxWidgets-2.9.1  --enable-optimize --with-crypto-prefix=/opt/local  --with-gdlib-config=/opt/local/bin/gdlib-config  --with-libiconv-prefix=/opt/local/var/macports/software/libiconv/1.13.1_0/opt/local/bin --enable-cas --enable-webserver  --enable-amulecmd --enable-amule-gui --enable-wxcas --enable-alc --enable-alcc --enable-amule-daemon --enable-geoip  --with-geoip-lib=/opt/local/var/macports/software/libgeoip/1.4.6_0/opt/local --with-geoip-headers=/opt/local/var/macports/software/libgeoip/1.4.6_0/opt/local/include --enable-geoip-static --enable-debugThe parts of the log that i consider interesting:
Code: [Select]
checking gd.h usability... yes
checking gd.h presence... no
configure: WARNING: gd.h: accepted by the compiler, rejected by the preprocessor!
configure: WARNING: gd.h: proceeding with the compiler's result
checking for gd.h... yes

checking for GeoIP_open in -lGeoIP... no
configure: WARNING:
        GeoIP support has been disabled because the GeoIP libraries were not found

checking for wxWidgets version >= 2.8.8 (--unicode=yes)... yes (version 2.9.1)
checking if wxWidgets was built in DEBUG mode... no
checking if wxWidgets was built in STATIC mode... yes
gtk2

checking if the linker (ld) is GNU ld... no

checking for bfd... no
configure: WARNING:
        bfd.h not found or unusable, please install binutils development
        package if you are a developer or want to help testing aMule

  Configure script has finished system check.

  Configured aMule SVN (rev. 10306) for 'i686-apple-darwin10.4.0'.

  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?          disabled
  Should aMule monolithic application be built?              yes
  Should aMule daemon version be built?                      yes
  Should aMule remote gui be built? (EXPERIMENTAL)           yes
  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?                     no
  Should plasmaMule plasma-applet be build?                  no

  **** General Libraries and Tools ****
  Should ccache support be enabled?                          no
  Libraries aMule will use to build:
                                       wxWidgets             2.9.1 (gtk2,static)
                                       crypto++              5.6.1 (installed, in /opt/local)
                                       libupnp               1.6.6
                                       libintl               included
                                       libpng                1.2.44
                                       libgd                 2.0.35
                                       zlib                  1.2.3


 *** Warnings during configuration ***

* GeoIP support has been disabled because the GeoIP libraries were not found

* bfd.h not found or unusable, please install binutils development package ifyou are a developer or want to help testing aMule

Is something useful?
Logged

^marcell^

  • Developer
  • Hero Member
  • *****
  • Karma: 28
  • Offline Offline
  • Posts: 524
Re: Compilation problem
« Reply #10 on: October 07, 2010, 05:43:07 PM »
Can you post the output of "ls -l /Users/admin/Desktop/aMuleSVN/wxWidgets-2.9.1" ?
Logged

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Re: Compilation problem
« Reply #11 on: October 07, 2010, 06:34:22 PM »
The log is 50.00+ characters long. I cannot post it. How can I do?
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Compilation problem
« Reply #12 on: October 07, 2010, 07:24:27 PM »
Why is port gtk2?
Logged

markellos

  • Approved Newbie
  • *
  • Karma: -1
  • Offline Offline
  • Posts: 23
Re: Compilation problem
« Reply #13 on: October 07, 2010, 07:58:40 PM »
Quote from: Kry on October 07, 2010, 07:24:27 PM
Why is port gtk2?

Ehm...what should it be?
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Compilation problem
« Reply #14 on: October 07, 2010, 10:39:07 PM »
In your case? whatever port wxwidgets reports. Chances are osx_cocoa or something similar if it's 2.9. Check it on the summary after running configure on wx.
Logged
Pages: [1] 2 3 4
« previous next »