aMule Forum

English => Compilation problems => Topic started by: vdb on November 15, 2009, 03:17:42 PM

Title: Compilation problems on Solaris 10 u8
Post by: vdb on November 15, 2009, 03:17:42 PM
I do hope somebody can help me out here. For specific reasons I have installed a machine with Solaris 10 u8. But to compile and run aMule on it is becoming a bit of a struggle.

I have downloaded and compiled wxWidgets 2.8.10 with GTK2, and also compiled Cryptopp 5.6.0. Both seemed to compile without error. Now I try to compile aMule and it gives the me this output:
  Configure script has finished system check.

  Configured aMule 2.2.6 for 'i386-pc-solaris2.10'.

  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?               no
  Should aMule be compiled with UPnP support?                no
  Should aMule be compiled with IP2country support?          no
  Should aMule monolithic application be built?              yes
  Should aMule daemon version be built?                      no
  Should aMule remote gui be built? (EXPERIMENTAL)           no
  Crypto++ library/headers style?                            sources

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

  **** aMule WebServer ****
  Should aMule WebServer be built?                           no

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

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

  **** aMule Statistics ****
  Should C aMule Statistics (CAS) be built?                  no
  Should aMule GUI Statistics (wxCas) be built?              no

  **** General Libraries and Tools ****
  Should ccache support be enabled?                          no
  Libraries aMule will use to build:
                                       wxWidgets             2.8.10 (gtk2,shared)
                                       crypto++              5.6.0 (sources, in )
                                       libintl               system
                                       zlib                  1.2.3

So configure works out that everything necessary is here.

The actual compilation, using "gmake" runs until the linking of aMule:
<snip>
Compiling TerminationProcess.cpp
Compiling TerminationProcessAmuleweb.cpp
Compiling UserEvents.cpp
Compiling OtherFunctions.cpp
Compiling NetworkFunctions.cpp
Linking amule
Undefined                       first referenced
 symbol                             in file
CMSG_LEN                            /opt/csw/lib/libgio-2.0.so.0
CMSG_SPACE                          /opt/csw/lib/libgio-2.0.so.0
ld: fatal: Symbol referencing errors. No output written to amule
collect2: ld returned 1 exit status
gmake[3]: *** [amule] Error 1
gmake[2]: *** [all-recursive] Error 1
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2

Anybody have an idea what is wrong?

The odd thing is that this compilation actually did work earlier. But I think I decided to recompile wxWidgets for some reason, with different options. Could that be my problem, that I recompiled with the configure option "--with-GTK2"?

And before you ask, the /opt/csw/lib is in the LD_LIBRARY_PATH environment variable.
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 16, 2009, 05:45:50 AM
Hi!

There are two things I would like to point:

1. There's an entry on the wiki about compiling aMule on solaris: http://wiki.amule.org/index.php/HowTo_compile_on_Solaris
2. It seems strange that the linking process is trying to link against libgio in /opt/csw instead of using the one included in Solaris.

I'll try to setup a VM with solaris 10 U8 and see if I can get the same problem.

Regards.
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 16, 2009, 07:10:54 PM
Yes, I know about that Wiki entry, and without it I would not even have made it this far I'd say. Thanks for that.

The reason it may link against /opt/csw rather than /opt/sfw may be the order in which I have put them into the environment:
CPPFLAGS='-I/usr/local/include -I/opt/csw/include -I/usr/sfw/include'
LDFLAGS='-L/usr/local/lib -R/usr/local/lib -L/opt/csw/lib -R/opt/csw/lib -L/usr/sfw/lib -R/usr/sfw/lib'
LD_LIBRARY_PATH=/usr/local/lib:/opt/csw/lib:/usr/sfw/lib:/usr/lib

PATH=/opt/csw/bin:/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/usr/ccs/bin:/usr/sfw/bin:/usr/local/bin

Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 16, 2009, 07:26:26 PM
When I wrote my reply I started to think that changing the order of the includes and such could make a difference and indeed it does. Now I have another interesting error, can't even get through configure:
configure:2116: $? = 0
configure:2118: g++ -v </dev/null >&5
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs
Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)
configure:2121: $? = 0
configure:2123: g++ -V </dev/null >&5
g++: `-V' option must have argument
configure:2126: $? = 1
configure:2149: checking for C++ compiler default output file name
configure:2152: g++  -I/usr/local/include I/usr/sfw/include -I/opt/csw/include -L/usr/local/lib -R/usr/local/lib -L/usr/sfw/lib -R/usr/sfw/lib -L/opt/csw/lib -R/opt/csw/lib conftest.cc  -lrt >&5
g++: I/usr/sfw/include: No such file or directory
configure:2155: $? = 1
configure: failed program was:
| /* confdefs.h.  */
|
| #define PACKAGE_NAME "aMule"
| #define PACKAGE_TARNAME "amule"
| #define PACKAGE_VERSION "2.2.6"
| #define PACKAGE_STRING "aMule 2.2.6"
| #define PACKAGE_BUGREPORT "admin@amule.org"
| #define PACKAGE "amule"
| #define VERSION "2.2.6"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2194: error: C++ compiler cannot create executables
See `config.log' for more details.

## ---------------- ##

This is with the following environment:
CPPFLAGS='-I/usr/local/include I/usr/sfw/include -I/opt/csw/include'
LDFLAGS='-L/usr/local/lib -R/usr/local/lib -L/usr/sfw/lib -R/usr/sfw/lib -L/opt/csw/lib -R/opt/csw/lib'
LD_LIBRARY_PATH=/usr/local/lib:/usr/sfw/lib:/usr/lib:/opt/csw/lib
PATH=/usr/sbin:/usr/bin:/usr/dt/bin:/usr/openwin/bin:/usr/sfw/bin:/usr/local/bin:/usr/csw/bin

So I reckon that maybe one of the variables must have /opt/csw before /opt/sfw, and another one use the reverse order. But which one should be wich?

Title: Re: Compilation problems on Solaris 10 u8
Post by: GonoszTopi on November 16, 2009, 10:57:01 PM
CPPFLAGS='-I/usr/local/include I/usr/sfw/include -I/opt/csw/include'
You're missing a '-' sign.
Code: [Select]
CPPFLAGS='-I/usr/local/include I/usr/sfw/include -I/opt/csw/include'
------------------------------^
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 18, 2009, 01:21:06 PM
Indeed I did mis that minus.

However, now I see the following at the end of configure:
config.status: creating po/Makefile
config.status: executing denoiser commands
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9
Unrecognized command:        /^MULEC\(XX\)\?FLAGS/! b 9


  Configure script has finished system check.

  Configured aMule 2.2.6 for 'i386-pc-solaris2.10'.

  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?               no
  Should aMule be compiled with UPnP support?                no
  Should aMule be compiled with IP2country support?          no
  Should aMule monolithic application be built?              yes
  Should aMule daemon version be built?                      no
  Should aMule remote gui be built? (EXPERIMENTAL)           no
  Crypto++ library/headers style?                            sources

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

  **** aMule WebServer ****
  Should aMule WebServer be built?                           no

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

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

  **** aMule Statistics ****
  Should C aMule Statistics (CAS) be built?                  no
  Should aMule GUI Statistics (wxCas) be built?              no

  **** General Libraries and Tools ****
  Should ccache support be enabled?                          no
  Libraries aMule will use to build:
                                       wxWidgets             2.8.10 (gtk2,shared)
                                       crypto++              5.6.0 (sources, in )
                                       libintl               included
                                       zlib                  1.2.3

These de-noiser commands, are they necessary?
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 18, 2009, 01:27:21 PM
Guess they are not really important, but I end up with the same error:

xWidgets-2.8.10/lib -pthreads -L/usr/local/lib -R/usr/local/lib -L/opt/csw/lib -R/opt/csw/lib -L/usr/sfw/lib -R/usr/sfw/lib  -L/usr/X11R6/lib  -L/usr/openwin/lib  -Wl,-R,/export/home/emule/compile/wxWidgets-2.8.10/lib -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8     -lgen  -lrt
Undefined                       first referenced
 symbol                             in file
FT_Select_Size                      /opt/csw/lib/libfontconfig.so.1
CMSG_LEN                            /opt/csw/lib/libgio-2.0.so.0
CMSG_SPACE                          /opt/csw/lib/libgio-2.0.so.0
ld: fatal: Symbol referencing errors. No output written to amule
collect2: ld returned 1 exit status
gmake[3]: *** [amule] Error 1
gmake[3]: Leaving directory `/export/home/emule/compile/aMule-2.2.6/src'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/export/home/emule/compile/aMule-2.2.6/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/export/home/emule/compile/aMule-2.2.6'
gmake: *** [all] Error 2
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 18, 2009, 01:30:23 PM
And one other thing, I only have one libgio-2.0.so.0:

-bash-3.00$ find / -name libgio-2.0.so.0
find: cannot read dir /data/postgresql: Permission denied
/opt/csw/lib/libgio-2.0.so.0

There is no "Solaris" version?
Title: Re: Compilation problems on Solaris 10 u8
Post by: GonoszTopi on November 18, 2009, 10:56:54 PM
About denoiser: you can "get rid of it" by passing --with-denoise-level=0 to configure (which is default for SVN tarballs). Although I tried to make the script as portable as possible, seems like it's not enough. :(
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 20, 2009, 05:35:11 PM
I did find some reference to my problem, I think, but since I only follow cookbooks to get things compiled I have no idea where to place this:

+++ src/fdpass.C       2008-08-09 00:41:29.000000000 +0000
 =20
 -#ifndef CMSG_LEN // CMSG_SPACE && CMSG_LEN are rfc2292 extensions to unix
 +// CMSG_SPACE & CMSG_LEN are rfc2292 extensions to unix
 +#ifndef CMSG_SPACE
 +# define CMSG_SPACE(len) (sizeof (cmsghdr) + len)
 +#endif
 +
 +#ifndef CMSG_LEN
  # define CMSG_LEN(len) (sizeof (cmsghdr) + len)
  #endif
 =20
 
Obviously this code snippet is totally out of context and meant for a completely different application, but could this be the answer if I insert it into some file?


Another post I found, about compiling Python on Solaris 8, suggested the following:
 "I set HAVE_FD_TRANSFER = 0 and now that is working."

Any idea if aMule uses that macro?
Title: Re: Compilation problems on Solaris 10 u8
Post by: Stu Redman on November 20, 2009, 07:12:52 PM
CMSG_LEN is a symbol referenced in an external lib, and not a preprocessor constant. It's the linker that complains, not the compiler. So I don't think that could help.
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 21, 2009, 03:36:05 AM
OK, I just updated my wiki entry about compiling aMule on Solaris (English only, I don't know German) with some tips and tricks, and tested it with Solaris 10 U8, and I got aMule to compile. Please check again the wiki, maybe you made something different that will not let aMule compile.

Edit: It compiles, but amuled and amule segfault on start, so there's something definitely wrong with my process of compiling. I'll recheck and see what can it be.
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 21, 2009, 01:05:51 PM
Yeah, that's basically where I was the first time after I followed your Wiki entry, aMule compiled but segfaulted and left me with nice core dumps.

Since then however I started making changes which made it so that the compilation didn't work, so I'll have to get back to the original configuration. Maybe the real difference between then and now is that I started to include "--enable-debug" and "--disable-optimize".

But even using your complete configure line I just can't get rid of this libgio symbol error. What package could I have added that changed the environment?


Update: If I put /opt/csw/bin as the first entry in my PATH the de-noiser commands actually do work. The linker still fails though.
But even then the configure script still can't find "iconv", even though it's clearly located in /opt/cws/bin and I can call it from the command line. Another mystery?
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 21, 2009, 04:44:11 PM
I am working on that right now. Some years ago (like 2 or 3) I remember I had the exact same issue (solaris compiled but segfaulted). It was somehow related to libintl and libiconv, but I cannot find my notes where I documented how to solve it. I'll try to get a solution, and will post here and update the wiki.

Regards.
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 21, 2009, 06:10:06 PM
I did some more testing with other configure options, because until now I used only the bare minimum of aMule's. And now when I include "--enable-wxcas" I get exactly the same linker error:

Building libmulecommon.a
Compiling cas.c
Compiling configfile.c
Compiling functions.c
Compiling graphics.c
Compiling html.c
Compiling lines.c
Linking cas
Compiling onlinesig.cpp
Compiling linuxmon.cpp
Compiling wxcas.cpp
Compiling wxcasprint.cpp
Compiling wxcasframe.cpp
Compiling wxcasprefs.cpp
Compiling wxcascte.cpp
Compiling wxcaspix.cpp
Linking wxcas
Undefined                       first referenced
 symbol                             in file
CMSG_LEN                            /opt/csw/lib/libgio-2.0.so.0
CMSG_SPACE                          /opt/csw/lib/libgio-2.0.so.0
ld: fatal: Symbol referencing errors. No output written to wxcas
collect2: ld returned 1 exit status
gmake[5]: *** [wxcas] Error 1
gmake[4]: *** [all-recursive] Error 1
gmake[3]: *** [all-recursive] Error 1
gmake[2]: *** [all-recursive] Error 1
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2

So the error does NOT occur when it links "cas", but it does when it links "wxcas". Ergo, there must be something with the wxWidget compilation or installation of mine.

I realise that we are diverging a bit in problems: Not being able to compile vs segfaulting after compilation.

Let's keep this thread about getting the compiler to finish?
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 21, 2009, 06:46:08 PM
Hi!

I just made some type of progress: I tried compiling with cryptopp 5.5.2 instead of 5.6.0. Now, amuled will start:

Code: [Select]
-bash-3.00$ ./Desktop/aMule-2.2.6/src/amuled
amuled: OnInit - starting timer
Initialising aMuled 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running...
No other instances are running.
ERROR: Info  --- This is the first time you run aMule 2.2.6 ---


More information, support and new releases can found at our homepage,
at www.aMule.org, or in our IRC channel #aMule at irc.freenode.net.

Feel free to report any bugs to http://forum.amule.org
ListenSocket: Ok.
Loading temp files from /home/gpulido/.aMule/Temp.

All PartFiles Loaded.
No shareable files found in directory: /home/gpulido/.aMule/Incoming

ERROR: aMule daemon cannot be used when external connections are disabled. To enable External Connections, use either a normal aMule, start amuled with the option --ec-config or set the key"AcceptExternalConnections" to 1 in the file ~/.aMule/amule.conf

HTTP download thread started
Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
-bash-3.00$ uname -a
SunOS vmsolaris10 5.10 Generic_141445-09 i86pc i386 i86pc
-bash-3.00$

but amule monolithic stil crashes on start, with the core file reporting something about X libraries. I'll keep digging to see what I can find.

Regarding your wx issue, I suggest you to try compiling wxGTK disabling all CSW libraries. That is done by removing /opt/csw from any LD* environment variable, so it will not know that libraries exist. WXGtk is very solaris friendly, it will compile on a standard solaris 10 install just setting the correct path so it can find gcc and gmake. Also, try using the configure line I used on the wiki, and always run "gmake" instead of "make".

Regards.
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 21, 2009, 07:38:03 PM
I just figured out my total stupid mistake regarding the linking: I have been re-compiling wxWidgets with different compiler environment settings than I was compiling aMule: 2 Different logins, 2 different shells.

So, now that I have in fact re-compiled wxWidgets in the same environment that I compile aMule in, the linking continues without a hitch. How silly can one be.

In the meantime I did also recompile aMule for my ancient Mandriva (2006, don't laugh...) and that went in one run in about 35 mins, including re-compiling wxWidgets and Crypto 5.6, since I had those lying around anyway. Why can't life be so simple for Solaris  *snif*

I'll try to compile with Crypto 5.5 as well, see what the results are at my end.
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 21, 2009, 07:45:22 PM
Could it be something with the ZFS that I'm using? I think I remember something about that either on this forum or somewhere on the internet about applications having issues with that file system type.
Title: Re: Compilation problems on Solaris 10 u8
Post by: Stu Redman on November 21, 2009, 07:59:12 PM
How silly can one be.
That's just the way many complicated problems look after you finally found the solution. But simple and simple to find are two entirely different issues. So don't mind, we all have felt that way often enough.  :D
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 21, 2009, 09:20:22 PM
Well, Cryptopp 5.5.2 is a bust. At least the package from Blastwave won't work, new and major linking problems with another undefined symbol.

Something weird when I compiled Cryptopp 5.5.2: It tried to use a command "ranlib", which is not found. Doesn't seem to influence the result though?

And we're breathing:
-bash-3.00$ ./amule
Initialising aMule 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
HTTP download thread started
Loading temp files from /export/home/emule/.aMule/Temp.

All PartFiles Loaded.
No shareable files found in directory: /export/home/emule/.aMule/Incoming
Assertion failed: XCB_SEQUENCE_COMPARE(xcb_req, >=, dpy->request), file xcb_lock.c, line 77
Abort (core dumped)

Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 21, 2009, 09:25:03 PM
Succes! Well, partial: amuled is running, so it seems.

Yep, after some configuring, amuled is running, amuleweb is started automagically and it is hashing some files. This is basically what I need to have, so for now I'll leave it at this.

So our solution is, at least for now: Use cryptopp 5.5.2, not 5.6.0.

PS: A quad core intel i920 is awfully fast at hashing, over 5 GB per minute!
PS2: And now another strange succes since I can connect to this amuled with my Vista amuleGUI!
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 22, 2009, 03:27:46 AM
-bash-3.00$ ./amule
Initialising aMule 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
HTTP download thread started
Loading temp files from /export/home/emule/.aMule/Temp.

All PartFiles Loaded.
No shareable files found in directory: /export/home/emule/.aMule/Incoming
Assertion failed: XCB_SEQUENCE_COMPARE(xcb_req, >=, dpy->request), file xcb_lock.c, line 77
Abort (core dumped)



ranlib in solaris is /usr/sfw/bin/granlib. It's one of the symbolic links you should create when I suggest to create the links to the GNU utils. Regarding the assertion, it's exactly the same error I'm getting. I could get over it by compiling aMule with no libiconv/libintl support, therefore there's no i18 support. But at least that wat, amule starts and works with no problems. I'll see what can I do to get a full aMule again, and update the wiki.

Regards.
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 22, 2009, 11:03:36 AM
Well, unfortunately all is not well in Solaris land yet: amuled crashes when a file completes download.

I get something like this in the logfile, "Suspending upload of file: E519157AC843A5DF9EE92FC6" and then it ends. Core dumps all over the place. This is too bad, if I can't use it yet  :(
Title: Re: Compilation problems on Solaris 10 u8
Post by: Stu Redman on November 22, 2009, 11:42:12 AM
Backtrace?
Make sure you do not enable mmap (you probably don't).  And compile with debug infos please.
And I don't think --disable-embedded-crypto is a valid switch anymore. Embedded crypto was kicked out some time ago. Bad idea seeing the cryptopp problems we are having ever since.  :(
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 22, 2009, 12:11:54 PM
yeah, backtrace. First I'll have to compile the GNU debug utils  :)

Skolnick probably already has this installed, I hope.....

PS. I just found that the gdb package is in fact available on Blastwave, so I hope to be able to post in the backtrace forum soon...
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 29, 2009, 02:59:48 AM
OK, I just traced the problem of amule segfaulting on start. It all seems to happen because of a bug in aMule (which strangely it doesn't happen on another platforms). It's (from what I read) some kind of race condition, no idea where. Compiling with debug enabled fails on my solaris, amule won't link, therefore I can't produce backtraces. The important thing is that I just discovered that removing blastwave's libxcb (CSWlibxcb package) aMule compiles and works fine. Now, the problem with that is that removing that library breaks blastwave's gd library, which is needed by amuleweb (there's no complete happiness, uh?) so the solution would be compiling gd from source. But that's also troublesome. I'm still working on this, and as soon as I get aMule compiling and working completely, I'll post it here and update the wiki.

On unrelated news, upnp is broken on solaris, since it will return UPNP_E_INIT_FAILED on aMule startup, and ports are not open on the router. I'm no developer, therefore I think I cannot solve this, but any clue about it will be welcome.

Regards.
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on November 29, 2009, 03:41:02 AM
OK, I just got aMule to compile complete with all its tools on Solaris again!! woohoo!!. The wiki entry has also been updated. It worked for me, but I would like a lot if anybody else can test it. Be warned that even when libUPnP compiles, it will not work (see previous post). I'll see what I can do, but this might be well beyond my current knowledge.

Regards.

P.S: Really nice new avatar, Stu...
Title: Re: Compilation problems on Solaris 10 u8
Post by: vdb on November 29, 2009, 11:12:53 AM
Good news.

Maybe unrelated, but I have been running aMuled on Solaris in debug mode, without optimizations, without upnp and without GeoIP for a week now. Without any hitches, I can even use gdb for backtraces   :)

The one thing that won't start for me is amulegui from Solaris. Somehow that just won't go beyond the "connecting" message. But since the Windows GUI connects that's not really a problem for me.

I'll check your updated wiki and see if it compiles again for me with those instructions. And I'll go make a nice SMF start for amuled.
Title: Re: Compilation problems on Solaris 10 u8
Post by: Stu Redman on November 29, 2009, 11:59:40 AM
P.S: Really nice new avatar, Stu...
Thank you!  :D
Just had to put it up after that awesome concert of her I visited on Wednesday.  :-*
Title: Re: Compilation problems on Solaris 10 u8
Post by: GonoszTopi on November 29, 2009, 09:03:11 PM
Now, the problem with that is that removing that library breaks blastwave's gd library, which is needed by amuleweb

amuleweb requires libpng not gd. gd is an optional requirement for cas (required to produce stats image).
Title: Re: Compilation problems on Solaris 10 u8
Post by: skolnick on December 05, 2009, 08:12:25 PM
Now, the problem with that is that removing that library breaks blastwave's gd library, which is needed by amuleweb

amuleweb requires libpng not gd. gd is an optional requirement for cas (required to produce stats image).

Ah! I didn't knew that, GonoszTopi...however it's good to have aMule with all of its functions working, and since I use cas to produce my online signature, I need it to have stats images support.

Regards.