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 8176 times)

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Compilation broken for compiler !=gcc
« on: November 27, 2007, 08:19:34 PM »

I've tried to build aMul 2.1.3 on a laptop running Sun's Solaris 10 (x86 version). The code configures OK, detecting my compiler is not gcc, but then throws a load of gcc specific flags at the compiler. Flags like -Wall, Wshadow and many more should not be used unless the compiler is gcc. The whole point of a configure script it to work out what the system needs - not to determine the compiler is not gcc, then give it a load of gcc flags anyway.

There are good reasons for not using gcc on many platforms. Generally speaking, the compilers from companies like Sun (on Solaris), HP (on HP-UX) etc produce smaller/faster code than gcc.

FWIW, this is my compiler:
bash-3.00$ cc -V
cc: Sun C 5.9 SunOS_i386 Build47_dlight 2007/05/22
usage: cc [ options] files.  Use 'cc -flags' for details



bash-3.00$ gmake
gmake  all-recursive
gmake[1]: Entering directory `/export/home/drkirkby/aMule-2.1.3'
Making all in m4
gmake[2]: Entering directory `/export/home/drkirkby/aMule-2.1.3/m4'
gmake[2]: Nothing to be done for `all'.
gmake[2]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/m4'
Making all in docs
gmake[2]: Entering directory `/export/home/drkirkby/aMule-2.1.3/docs'
Making all in man
gmake[3]: Entering directory `/export/home/drkirkby/aMule-2.1.3/docs/man'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/docs/man'
gmake[3]: Entering directory `/export/home/drkirkby/aMule-2.1.3/docs'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/docs'
gmake[2]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/docs'
Making all in src
gmake[2]: Entering directory `/export/home/drkirkby/aMule-2.1.3/src'
Making all in libs
gmake[3]: Entering directory `/export/home/drkirkby/aMule-2.1.3/src/libs'
Making all in ec
gmake[4]: Entering directory `/export/home/drkirkby/aMule-2.1.3/src/libs/ec'
gmake  all-am
gmake[5]: Entering directory `/export/home/drkirkby/aMule-2.1.3/src/libs/ec'
source='ECPacket.cpp' object='libec_noevt_a-ECPacket.o' libtool=no \
        DEPDIR=.deps depmode=none /bin/bash ../../../depcomp \
        CC -DHAVE_CONFIG_H -I. -I. -I../../..    -I/usr/local/lib/wx/include/motif-ansi-release-2.6 -I/usr/local/include/wx-2.6 -D__WXMOTIF__ -I/usr/openwin/include -I/usr/dt/include -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES   -I../../../src -I../../../src/libs -DECSOCKET_USE_EVENTS=0 -DUSE_EMBEDDED_CRYPTO -W -Wall -Wshadow -Wundef -g -ggdb -fno-inline -D__DEBUG__ -fmessage-length=0 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC   -c -o libec_noevt_a-ECPacket.o `test -f 'ECPacket.cpp' || echo './'`ECPacket.cpp
CC: Warning: Option -W passed to ld, if ld is invoked, ignored otherwise
CC: Warning: Option -Wall passed to ld, if ld is invoked, ignored otherwise
CC: Warning: Option -Wshadow passed to ld, if ld is invoked, ignored otherwise
CC: Warning: Option -Wundef passed to ld, if ld is invoked, ignored otherwise
CC: Warning: Option -ggdb passed to ld, if ld is invoked, ignored otherwise
CC: Warning: Option -fno-inline passed to ld, if ld is invoked, ignored otherwise
CC: Warning: Option -fmessage-length=0 passed to ld, if ld is invoked, ignored otherwise
"../../../src/ArchSpecific.h", line 99: Error: Badly formed constant expression.
"ECSocket.h", line 284: Warning: CECSocket::Connect hides the virtual function wxSocketClient::Connect(wxSockAddress&, bool).
1 Error(s) and 1 Warning(s) detected.
gmake[5]: *** [libec_noevt_a-ECPacket.o] Error 1
gmake[5]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/src/libs/ec'
gmake[4]: *** [all] Error 2
gmake[4]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/src/libs/ec'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/src/libs'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/export/home/drkirkby/aMule-2.1.3/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/export/home/drkirkby/aMule-2.1.3'
gmake: *** [all] Error 2
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Compilation broken for compiler !=gcc
« Reply #1 on: November 27, 2007, 08:27:53 PM »

We definitely not support anything other than gcc (and maybe MSVC soon) but you're very welcome to post patches :)
Logged

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: Compilation broken for compiler !=gcc
« Reply #2 on: November 27, 2007, 08:46:59 PM »

Why not?

Plenty of other software builds fine on Sun compilers - wxWidgets being one such program. The UNIX world did not start wtih Linux or gcc and it does not end with it either! Would it not be more sensible to write scripts wtih a view to portability?

My guess is a lot of the flags you use are probably unnecessary anyway. Why do you need "-ggdb"? ~My guess is that -g would do fine and would be portable. Some, such as -Wall I can see the point of, but would it not be sensible to test for gcc first?

My own experience is that testing code on many platforms tends to remove a lot of bugs. Solaris is free - in fact Sun will even send one a DVD wtih the latest developer  edition and Sun pay the postage!!!

http://www.sun.com/software/solaris/solaris-express/get.jsp

Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Compilation broken for compiler !=gcc
« Reply #3 on: November 27, 2007, 09:22:12 PM »

I'm not saying we're against it, I'm saying that it will definitely not work out of the box. and you're welcome to contribute :)
Logged

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: Compilation broken for compiler !=gcc
« Reply #4 on: November 28, 2007, 12:30:42 AM »

I'm not saying we're against it, I'm saying that it will definitely not work out of the box. and you're welcome to contribute :)

I realise you were not against it, but perhaps taking a more active role for it, might be useful.  :) There are two ways to get this to work on Solaris with a compiler other than gcc.

1) Make numerous Solaris sections. This would help create something that runs under Solaris, but would be of no help to users on AIX, HP-UX, or any other system. It would also be hard to maintain.

2) Remove all the gcc specific flags, unless they are  necessary. That would have the advantage of getting it to work on other systems too. There seems to be a lot of flags I suspect could be removed from the configure.in on Linux, but I'm not in a posittion to check this.

For example, do you really need -ggdb ?? I would have thought that on a Linux (I assume your main users), then the flag -g would be sufficient to produce something that the usual tools on linux would be able to debug. Am I wrong? If I attempted to compile on Solaris using gcc with only the -g flag, it would be very easy to debug using gdb. If I compiled on Solaris with Sun's compiler and used -g, it would be easy to debug using Suns tools. ~In other words, using -g for debugging would work on Linux, Solaris and most other platforms I am aware of. As soon as you add the -ggdb flag, it becomes a very gcc specififc thing.

Looking at just one line in the configure.in, I see:


-W -Wall -Wshadow -Wundef -g -ggdb -fno-inline -D__DEBUG__ -fmessage-length=0 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEB
UG_PEDANTIC

My guess is that -fno-inline is not needed either. I assume that stops the compiler inlining functions, which I doubt it would do if you used -g.

Likewise, is there a need for -Wshadow,  if -Wall is used?

I may be wrong (if so correct me), but I get the feeling a lot of these flags have been inherited from others and have not been checked if they are ally needed or no.





Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Compilation broken for compiler !=gcc
« Reply #5 on: November 28, 2007, 12:43:48 AM »

Could you please remove these flags and do some testing? Even though I have the Solaris DVD you mentioned above, I have only (Arch)Linux and OpenBSD installed, any help from your side is much appreciated.
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 #6 on: November 28, 2007, 01:20:55 AM »

drkirkby,

Please, post a patch against our CVS tarball that you consider ok so that we can have a chance to analise it and discuss. I will surely commit it if there are no problems on other platforms. What I can't do is create a patch like that which can affect compilation and which I am not able to test, that would be a waste of time. Unfortunately I have no Solaris here and I have no resources to install it.

Thanks for your support!
Logged

skolnick

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

I could also try to compile using SunStudio and Solaris 10 Update 4 (x86). However, I've found aMule builds and works really well with gcc. Also, there is another problem: last time I checked (wxGTK 2.8.4 I think) wxGTK would not build with unicode support (required by aMule) using SunStudio 11, but I suspect the result would be the same with any SunStudio version .

Regards.
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Compilation broken for compiler !=gcc
« Reply #8 on: November 28, 2007, 06:11:26 AM »

Er... something to note. -ggdb will NOT be remoted, because it gives extra information for debugging for gdb in linux. If it doesn't work with other compiler different form gcc, then it has to be addresed to not use it on that compiler, but NEVER remove flags just because you don't like them or think they are superfluous even if they ADD functionality.
Logged

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: Compilation broken for compiler !=gcc
« Reply #9 on: November 28, 2007, 07:00:10 AM »

I've downloaded the latest aMule CVS and tried to build that, so I could patch the configure.in script.

Unfortunately, the aMule configure script in CVS stops with:

" The configuration you asked for aMule requires a wxWidgets
    build with the following settings:
        --unicode=yes
    but such build is not available.
"

But trying to build wxWidgets with uniconde support is not possible as you say, as wxWidget's configure script stops with:

 ./configure --enable-unicode
<snip>
configure: error: Unicode configuration not supported with Motif

So it seems the aMule 2.1.3 has some hope of building on my system, but the latest CVS, which needs unicode support from wxWidgets, is unlikly to be very easy to build at all. As such, I do not think I am going to be able to create a usable patch file.

I looked into the autoconf documentation, and see that the macro AC_PROG_CC sets the variable GCC to "yes" if the GNU C compiler is used. Since that macro is used in the configure script for aMule, I guess it would be easy to test for gcc before adding flags that are gcc specific.

Whilst I have not tested this with the latest CVS (for reasons I explained above), I think the following would be a simple thing to add to the configure script before adding gcc-specific flags, after AC_PROG_CC


if test x$GCC = xyes; then
DEBUG_FLAGS="-W -Wall -Wshadow -Wundef -g -ggdb -fno-inline -D__DEBUG__ -fmessage-length=0 -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC"
else
DEBUG_FLAGS="-g -D__DEBUG__ -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC "
fi

That way the flags lile -Wal, -W, -Wshadow, -Wundef  -ggdb would only be put on the gcc compiler, not another compiler. If similar was done when setting other flags, it would ensure flags which only gcc accepts are only sent to gcc.

Given the aMule in VCS needs unicode support, and wxWidgets does not support unicode on my system, I'm not sure there is much more I can do.

If any of the developers need access to a Solaris box (SPARC, not x86), then I  could make one available via ssh. I can't do it on Solaris x86 though, as I only have that on my laptop. But I do have another Sun which runs Solaris 10 and runs 24/7.











Logged

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: Compilation broken for compiler !=gcc
« Reply #10 on: November 28, 2007, 07:02:46 AM »

Er... something to note. -ggdb will NOT be remoted, because it gives extra information for debugging for gdb in linux. If it doesn't work with other compiler different form gcc, then it has to be addresed to not use it on that compiler, but NEVER remove flags just because you don't like them or think they are superfluous even if they ADD functionality.

I can see your point, but I think you should test for gcc before adding them. AC_PROG_CC should set the variable GCC to yes if using gcc, so I think the configure script should check if the compiler is gcc before adding flags that only gcc will understand.
« Last Edit: November 28, 2007, 07:06:25 AM by drkirkby »
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Compilation broken for compiler !=gcc
« Reply #11 on: November 28, 2007, 07:38:30 AM »

aMule 2.1.3 also require a unicode wxWidgets
Logged

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: Compilation broken for compiler !=gcc
« Reply #12 on: November 28, 2007, 08:34:52 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
-#              Verbose mode
-###            Show compiler commands built by driver, no compilation
-A<name[(tokens)]>      Preprocessor predicate assertion
-B<[static|dynamic]>    Specify dynamic or static binding
-C              Prevent preprocessor from removing comments
-c              Compile only - produce .o files, suppress linking
-D<name[=token]>        Associate name with token as if by #define
-d[y|n]         dynamic [-dy] or static [-dn] option to linker
-E              Compile source through preprocessor only, output to stdout
-erroff=<t>     Suppress warnings specified by tags t(%none, %all, <tag list>)
-errshort[=<a>] Control amount of type details in error messages, <a>={short|full|tags}
-errtags=<a>    Display messages with tags a(no, yes)
-errwarn=<t>    Treats warnings specified by tags t(%none, %all, <tag list>) as errors
-fast           Optimize using a selection of options
-fd             Report old-style function definitions and declarations
-features=<v>   Enable/disable C language features, <v>= {[no%]extinl|[no%]typeof|[no%]extensions}
-flags          Show this summary of compiler options
-flteval[=<a>]  Evaluation of floating point expressions, a={2|any}
-fnonstd        Initialize floating-point hardware to non-standard preferences
-fns[=<yes|no>] Select non-standard floating point mode
-fprecision=<p> Set FP rounding precision mode p(single, double, extended)
-fround=<r>     Select the IEEE rounding mode in effect at startup
-fsimple[=<n>]  Select floating-point optimization preferences <n>
-fsingle        Use single-precision arithmetic (-Xt and -Xs modes only)
-ftrap=<t>      Select floating-point trapping mode in effect at startup
-fstore         force floating pt. values to target precision on assignment
-G              Build a dynamic shared library
-g              Compile for debugging
-H              Print path name of each file included during compilation
-h <name>       Assign <name> to generated dynamic shared library
-I<dir>         Add <dir> to preprocessor #include file search path
-i              Passed to linker to ignore any LD_LIBRARY_PATH setting
-keeptmp        Keep temporary files created during compilation
-KPIC           Compile position independent code with 32-bit addresses
-Kpic           Compile position independent code
-L<dir>         Pass to linker to add <dir> to the library search path
-l<name>        Link with library lib<name>.a or lib<name>.so
-m32            set 32-bit addressing model
-m64            set 64-bit addressing model
-mc             Remove duplicate strings from .comment section of output files
-mr             Remove all strings from .comment section of output files
-mr,"string"    Remove all strings and append "string" to .comment section
-mt             Specify options needed when compiling multi-threaded code
-native         Optimize for the host system (-xtarget=native)
-nofstore       Do not force floating pt. values to target precision on assignment
-O              Use default optimization level (-xO3)
-O<n>           Same as -xO<n>
-o <outputfile> Set name of output file to <outputfile>
-P              Compile source through preprocessor only, output to .i  file
-p              Compile for profiling with prof
-Q[y|n]         Emit/don't emit identification info to output file
-qp             Compile for profiling with prof
-R<dir[:dir]>   Build runtime search path list into executable
-S              Compile and only generate assembly code (.s)
-s              Strip symbol table from the executable file
-U<name>        Delete initial definition of preprocessor symbol <name>
-V              Report version number of each compilation phase
-v              Do stricter semantic checking
-W<c>,<arg>     Pass <arg> to specified component <c> (a,l,m,p,0,h,i,u)
-w              Suppress compiler warning messages
-Xa             Compile assuming ANSI C conformance, allow K & R extensions (default mode)
-Xc             Compile assuming strict ANSI C conformance
-Xs             Compile assuming (pre-ANSI) K & R C style code
-Xt             Compile assuming K & R conformance, allow ANSI C
-xalias_level=<a>       Enable optimizations based on the specified alias_level
-xarch=<a>      Specify target architecture instruction set
-xautopar       Enable automatic loop parallelization
-xbuiltin[=<b>] When profitable inline, or substitute intrinsic functions for system functions, b={%all,%none}
-xc99[=<a>]     Enable ISO C99 features, <a>={all,none,[no_]lib}
-xcache=<c>     Define cache properties for use by optimizer
-xCC            Accept C++ style comments
-xchar=<v>      Treat type char as signed (<v> = s or signed) or unsigned (<v> = u or unsigned).
-xchar_byte_order=<o>   Specify multi-char byte order <o> (default, high, low)
-xchip=<c>      Specify the target processor for use by the optimizer
-xcrossfile[=<n>]       Enable optimization and inlining across source files, n={0|1}
-xcsi           Allow C source code using non-ISO C compliant locales
-xdebugformat=<a>       Selects the format of debugging information; <a>={dwarf|stabs}
-xdepend[=<yes|no>]     Analyze loops for data dependencies
-xdryrun        The same as -###
-xe             Perform only syntax/semantic checking, no code generation
-xF=<a>[,<a>]   Compile for later mapfile reordering and data fragmentation, <a>={[no%]func|[no%]gbldata|%all|%none}
-xhelp=<f>      Display on-line help information f(flags, readme)
-xinline=[<a>,...,<a>]  Attempt inlining of specified user routines, <a>={%auto,func,no%func}
-xipo[=<n>]     Enable optimization and inlining across source files, n={0|1|2}
-xipo_archive=<a>       Enable crossfile optimization including archive files, <a>={none|readonly|writeback}
-xinstrument=<a>        Enable/disable instrumentation for race detection tool, <a>=[no%]datarace
-xjobs=<n>      Maximum number of components compiler will fork in parallel
-xldscope=<a>   Indicates the appropriate linker scoping within the source program; <a>={global|symbolic|hidden}
-xlibmieee      Force IEEE 754 return values for math routines in exceptional cases
-xlibmil        Inline selected libm math routines for optimization
-xlibmopt       Link with optimized math library
-xlic_lib=sunperf       Link in the Sun supplied performance libraries
-xloopinfo      Show loops that parallelized
-xM             Generate makefile dependencies
-xM1            Generate makefile dependencies, but exclude /usr/include
-xmaxopt=[off,1,2,3,4,5]        maximum optimization level allowed on #pragma opt
-xMerge         Merge data segment into text segment
-xmodel=<a>     Specify memory model for 64-bit programs, a={small|kernel|medium|large}
-xnolib         Do not link with default system libraries
-xnolibmil      Cancel -xlibmil on command line
-xnolibmopt     Cancel -xlibmopt on command line
-xnorunpath     Do not build a runtime search path into the executable
-xO<n>          Generate optimized code (n={1|2|3|4|5})
-xopenmp=<a>    Enable OpenMP language extension <a>={noopt|parallel|none}
-xP             Print prototypes for function definitions
-xpagesize_heap=<a>     Controls the preferred page size for the heap, a={4K|2M|4M|default}
-xpagesize_stack=<a>    Controls the preferred page size for the stack, a={4K|2M|4M|default}
-xpagesize=<a>  Controls the preferred page size for the stack and for the heap, a={4K|2M|4M|default}
-xparallel      Perform parallel compilation
-xpch=<p>       Enable precompiled headers.  Collect data for, or use existing, PCH file <p>={auto|autofirst|{collect,use}:<file>[.cpch]}
-xpchstop=<file>        Specified include file marks end of initial common sequence of pre-processing directives for precompiled headers.
-xpentium       Generate code for the pentium processor
-xpg            Compile for profiling with gprof
-xprefetch[=<p>]        Specify instruction prefetch p (auto,no%auto,explicit,no%explicit)
-xprefetch_auto_type=<a>        Specify automatic indirect prefetch insertion for loops; <a>=[no%]indirect_array_access
-xprefetch_level[=<n>]  Controls the aggressiveness of the -xprefetch=auto option (n={1|2|3})
-xprofile=<p>   Collect data for a profile or use a profile to optimize <p>={{collect,use}[:<path>],tcov}
-xreduction     Recognize reduction operations in parallelized loops
-xregs=<r>      Specify the usage of optional registers
-xrestrict[=<f>]        Treat pointer valued function parameters as restricted f(%none,%all,<function-name list>)
-xs             Allow debugging without object (.o) files
-xsb            Compile for use with the WorkShop source browser
-xsbfast        Generate only WorkShop source browser information, no compilation
-xsfpconst      Represent unsuffixed floating point constants as single precision
-xspace         Do not do optimizations that increase code size
-xstrconst      Place string literals into read-only data segment
-xtarget=<t>    Specify target system for optimization
-xtemp=<dir>    Set directory for temporary files to <dir>
-xthreadvar=<a>[,<a>]   Control code generation for thread variables <a>={[no%]dynamic|[no%]stack|%all|%none}
-xtime          Report the execution time for each compilation phase
-xtransition    Emit warnings for differences between K&R C and ANSI C
-xtrigraphs[=<yes|no>]  Enable|disable trigraph translation
-xunroll=n      Enable unrolling loops n times where possible
-xustr=<a>      Recognize sixteen-bit string literals <a>={no|ascii_utf16_ushort}
-xvector[={[no%]lib,[no%]simd | %none}] automatic generation of calls to the vector library functions and/or the generation of the SIMD instructions.
-xvpara         Verbose parallelization warnings
-Y<c>,<dir>     Specify <dir> for location of component <c> (a,l,m,p,0,h,i,u)
-YA,<dir>       Change default directory searched for components
-YI,<dir>       Change default directory searched for include files
-YP,<dir>       Change default directory for finding libraries files
-YS,<dir>       Change default directory for startup object files
-Zll            Create lock_lint database files (.ll)

For additional product information or for the name of a Sun software
reseller, please call 1-800-786-7638, or (+1) 512-434-1511 (outside the US),
or fax your request to (+1) 512-218-3866.

For technical support, please contact your Sun software reseller for the
name of an Authorized Service Provider.

For more information, please browse http://docs.sun.com

To access the complete documentation set, go to the documentation index at file:/opt/SUNWspro/docs/index.html
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: Compilation broken for compiler !=gcc
« Reply #13 on: November 28, 2007, 08:43:25 AM »

Could you please try to use GTK2 as toolkit for wx? As far as I know, it works fine on Solaris and Sun started shipping some kind of GTK2-based desktop environment (GNOME) some years ago, so it should be supported.
Logged

drkirkby

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
Re: Compilation broken for compiler !=gcc
« Reply #14 on: November 28, 2007, 09:23:55 AM »

Could you please try to use GTK2 as toolkit for wx? As far as I know, it works fine on Solaris and Sun started shipping some kind of GTK2-based desktop environment (GNOME) some years ago, so it should be supported.
No problem, I will try that later today, both on x86 and SPARC, and let you know the results.
Logged
Pages: [1] 2