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]

Author Topic: Compilation broken for compiler !=gcc  (Read 8173 times)

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Compilation broken for compiler !=gcc
« Reply #15 on: November 30, 2007, 02:22:05 AM »

I can compile wxGTK using the --with-gtk=2 and it will not try motif.

Regards.
Logged

lfroen

  • Guest
Re: Compilation broken for compiler !=gcc
« Reply #16 on: December 02, 2007, 09:41:16 AM »

aMule 2.1.3 also require a unicode wxWidgets

At least on my box, the configure script did not notify me of that fact.

I'll try to build aMule and wxWidgets with gcc. But I think it would be generally a good idea if you could fix the configure script so it does not add gcc specific flags unless the compiler is gcc. Things like -c, -g, -O, -E,  -I,  and a few more are safe on any platfrom I know.

 FWIW, here are the flags Sun's compiler accepts.  It might give you some ideas of what ones the current script uses which are not universally used.

bash-3.00$ cc -flags
 <snip>

cc is C compiler. You need C++ compiler to build aMule. Do you know that gcc is ported to virtually every CPU architecture existing?! Except from some kind of masochistic pleasure, there's no reason to waste time on compiler issue like this.
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Compilation broken for compiler !=gcc
« Reply #17 on: December 02, 2007, 12:21:41 PM »

Just for the record: aMule compiles with llvm-gcc(4.2), but it segfaults upon start on x86_64. I'm sure whether it ran successfully the last time I tried it on my i686 machine a couple of months ago, but the compilation was a lot slower than with gcc.

Edit: In general it compiled faster code than gcc in less time for the C-code I tested, that's why I gave it a try.
« Last Edit: December 02, 2007, 12:24:35 PM by wuischke »
Logged

skolnick

  • Global Moderator
  • Hero Member
  • *****
  • Karma: 24
  • Offline Offline
  • Posts: 1188
  • CentOS 6 User
Re: Compilation broken for compiler !=gcc
« Reply #18 on: December 07, 2007, 02:03:16 AM »

cc is C compiler. You need C++ compiler to build aMule. Do you know that gcc is ported to virtually every CPU architecture existing?! Except from some kind of masochistic pleasure, there's no reason to waste time on compiler issue like this.
Some people likes using the native compiler of their platform (Solaris is compiled using SunPRO, not GCC), and I also think SunPRO has some performance gains when compared with GCC under some circumstances (no idea if aMule would benefit from them, however). I've also read that some software has ABI issues on solaris when compiled with GCC, therefore it is necessary to use SunPRO, however aMule seems not to have problems. I agree that it would be nice if aMule could be compiled with SunPRO, but since not even wxGTK can be compiled with it, I think it's useless to ask it from aMule.

Regards.
Logged

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Re: Compilation broken for compiler !=gcc
« Reply #19 on: December 18, 2007, 03:23:22 AM »

drkirkby,

Your patch to test for gcc before adding debug flags has been committed.

Thanks for your support.

Cheers!
Logged
Pages: 1 [2]