[kde-solaris] KDE 3.1.2 on solaris 8 with g++-v3.3.1

[Lars Tunkrans]

Jan Van Belle wrote:
> Laurent Blume wrote:
> 
>>Jan Van Belle wrote:
>>
>>
>>>With which version of gcc are you compiling (successfully)
>>>KDE??? Is it with the good old stable 2.95.3 or with one of
>>>the 3.x series??
>>
>>I just managed to compile KDE 3.1.3 with GCC 3.3.1 and GNU Binutils 2.14
>>on Solaris 9 x86. Works well :-)
>>
>>There were a few glitches:
>>   - some of them seems to be because the new GCC is more strict about
>>the code when -pedantic is used
>>   - some of them are C99 functions that GCC 3 does not support on
>>Solaris, such as fabsf()
>>   - some of them I didn't understand altogether, and deactivated the
>>build for the concerned part (kolf, kalarm).
>>
>>Overall, it was a bit harder to build KDE 3.1.3 w/ GCC3 than it had been
>>to build 3.1.0 w/ GCC2, on the same system.
>>
>>Not sure if it's only because of GCC or because of new bugs, though.
>>
>>Laurent
>>
> 
> Did you build gcc yourself too?? (if yes, can you give me
> the configuration options please??)
> I think my proble has something to do with the
> --with-local-prefix options (which I did not use in previous
> compiles)
> 
> Kind regards,


Hello,

This is for building  GCC-3.3  on SPARC Solaris9  default installation
into /usr/local

$ cd /opt/src/gcc-3.3/objdir
$ cat config.status

#!/bin/sh
# This file was generated automatically by configure.  Do not edit.
# This directory was configured as follows:
    ../configure --with-gcc-version-trigger=/opt/src/gcc-3.3/gcc/version.c
    --host=sparc-sun-solaris2.9 --with-as=/usr/ccs/bin/as
    --with-ld=/usr/ccs/bin/ld --disable-nls --with--languages=c,c++,objc,java --norecursion
# using "mh-frag"

-----------------

Then you need to set up the proper Environment variables to build KDE 3.1
I prefer to put all environment varaibles nessesary for a project  into a
kornshell RC-file which I usually name  .kshrc-something
Then export the kornshell $ENV  variable and start a new subshell.
That enables me to have several development setups whitout having to hack my
.profile  or .cshrc  file.


$ cd $HOME
$ more .kshrc-gcckde
CC=/usr/local/bin/gcc
CXX=/usr/local/bin/g++
CPPFLAGS="-I/usr/local/include -I/usr/sfw/include -I/opt/sfw/include"
LDFLAGS="-L//usr/local/lib -R/usr/local/lib -L/usr/sfw/lib -R/usr/sfw/lib -L/opt/sfw/lib -R/opt/sfw/lib -L/usr/ucblib -R/usr/ucblib"
CFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O3 -Wa,-xarch=v8plusa"
CXXFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O3 -Wa,-xarch=v8plusa"
QTDIR=/usr/local/qt
KDEDIR=/usr/local/kde
LD_LIBRARY_PATH=/usr/local/qt/lib:$LD_LIBRARY_PATH
export CC CXX CPPFLAGS LDFLAGS CFLAGS CXXFLAGS QTDIR KDEDIR LD_LIBRARY_PATH
PATH=/usr/bin:/usr/sbin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/local/bin:$QTDIR/bin:$KDEDIR/bin:/usr/sfw/bin:/opt/sfw/bin
export PATH



$ ENV=.kshrc-gcckde  export ENV
$ ksh -o vi


Then you are  ready to start compile source code.


Regards


-- 
========================================================
Lars Tunkrans
--------------------------------------------------------