ken mays | 1 Oct 2004 13:21
Picon
Favicon

Re: kde-solaris Digest, Vol 19, Issue 1


We know that you are very carefully porting kde to sparc arch, trying to
keep all the functionalities working, so we would appreciate very much
any help with this, if you could send us your patches, only referred to
functionality, not fot SunCC porting. We have problems with kdesu, and
the screen lock, would be very nice if we could really work as a team in
this issues, as we dont have to much time to spend on this, and we arent
skilled c coders.

Jaime.
--------------------->

1. Most of us are porting KDE to Solaris using GCC 3.3.x or 3.4.1.

2. Sun prefers developers to use Sun Studio 9 to port C/C++ to Solaris.

3. KDE.org should have volunteers designated to validate and test KDE compilation on Solaris 8/9/10 platforms using GCC. Post the results and configurations used to get a clean compile.

4. Solaris 10 isn't finalized yet, so if you get KDE 3.3.0 working on Solaris 10 then mentioned what build was used - as well as the compiler flags, GCC version, and any notes on getting a clean compile.

5. Some notes should be added for people wanting to compile KDE on Solaris 2.5.1 -> 2.7. Also notes for people wanting to compile KDE using Sun Studio 9. most of the information on the web is outdated from previous people porting KDE to Solaris.

6. Problems with GCC is that it changes ABI compatibility and you can compile things using GCC2 and then switch between GCC 3.4.2 and GCC 3.3.3. I haven't seen notes from anyone compiling KDE 3.3.0 using GCC v2.95.3 or v3.4.2 as the compiler on a Solaris platform. Would be nice to see somewhere!!!!!!

Just some notes to think about,

Ken Mays

(KDE maintainer/supporter at www.blastwave.org)

Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
Stefan Teleman | 1 Oct 2004 14:03
Picon

Re: KDE, Solaris, GCC, etc ...

I have uploaded a complete and full set of patches, both in xdelta 
format, and as full source code files, for KDE 3.3.0. I have done the 
same for KDE 3.2.2, 3.2.1 and 3.1.4. These patches are publicly 
available for download from any KDE mirror. There are also shell 
scripts for Forte compiler flags, environment variables, a modified 
libtool sample which can be used to build any KDE module, and shell 
scripts for running configure with the right flags for all the KDE 
modules.

And now for a litttle bit of history: when i set out to work on KDE on 
Solaris, at the beginning of 2003, it was agreed, on this list, that 
i will port, build and maintain KDE for Solaris with the Sun 
compilers. If i remember correctly, a vote was taken to this effect, 
by the members of this list.

There is no point for me, nor do i have any interest, in building KDE 
on Solaris with GCC. There is no point because it's been done 
already, by many people, and because Sun provides KDE built with GCC 
on their Companion CD. There are many other places on the 'Net where 
anyone can download KDE on Solaris built with GCC. I see no need for 
yet another GCC build. It is not very difficult to build KDE with 
GCC.

The point of building KDE with the Sun compilers is to show KDE, and 
Solaris, at their best. And because it is a very interesting project 
to work on, from a software engineering perspective. I don't believe 
that either of these two reasons apply when building with GCC. It's 
certainly not what i set out to do.

--Stefan

-----

On Friday 01 October 2004 07:21, ken mays wrote:
> We know that you are very carefully porting kde to sparc arch,
> trying to keep all the functionalities working, so we would
> appreciate very much any help with this, if you could send us your
> patches, only referred to functionality, not fot SunCC porting. We
> have problems with kdesu, and the screen lock, would be very nice
> if we could really work as a team in this issues, as we dont have
> to much time to spend on this, and we arent skilled c coders.
>
> Jaime.
> --------------------->
>
> 1. Most of us are porting KDE to Solaris using GCC 3.3.x or 3.4.1.
>
> 2. Sun prefers developers to use Sun Studio 9 to port C/C++ to
> Solaris.
>
> 3. KDE.org should have volunteers designated to validate and test
> KDE compilation on Solaris 8/9/10 platforms using GCC. Post the
> results and configurations used to get a clean compile.
>
> 4. Solaris 10 isn't finalized yet, so if you get KDE 3.3.0 working
> on Solaris 10 then mentioned what build was used - as well as the
> compiler flags, GCC version, and any notes on getting a clean
> compile.
>
> 5. Some notes should be added for people wanting to compile KDE on
> Solaris 2.5.1 -> 2.7. Also notes for people wanting to compile KDE
> using Sun Studio 9. most of the information on the web is outdated
> from previous people porting KDE to Solaris.
>
> 6. Problems with GCC is that it changes ABI compatibility and you
> can compile things using GCC2 and then switch between GCC 3.4.2 and
> GCC 3.3.3. I haven't seen notes from anyone compiling KDE 3.3.0
> using GCC v2.95.3 or v3.4.2 as the compiler on a Solaris platform.
> Would be nice to see somewhere!!!!!!
>
> Just some notes to think about,
>
> Ken Mays
>
> (KDE maintainer/supporter at www.blastwave.org)
>
>
>
> ---------------------------------
> Do you Yahoo!?
> vote.yahoo.com - Register online to vote today!

--

-- 
Stefan Teleman          'Nobody Expects the Spanish Inquisition'
steleman <at> nyc.rr.com                          -Monty Python

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Picon

Re: Re: KDE, Solaris, GCC, etc ...


Stefan Teleman wrote:
|
| And now for a litttle bit of history: when i set out to work on KDE on
| Solaris, at the beginning of 2003, it was agreed, on this list, that
| i will port, build and maintain KDE for Solaris with the Sun
| compilers. If i remember correctly, a vote was taken to this effect,
| by the members of this list.
|

We built kde 3.1.5 and 3.2.1 for our own purpose as your 3.1.4 seemed to
work too slow on our machines. The performance was notably increased, so
we wanted to share it with the official site. The sysadmin of kde told
us if we wanted to package the 3.2.2 version and continue releasing the
next versions.

| There is no point for me, nor do i have any interest, in building KDE
| on Solaris with GCC. There is no point because it's been done
| already, by many people, and because Sun provides KDE built with GCC
| on their Companion CD. There are many other places on the 'Net where
| anyone can download KDE on Solaris built with GCC. I see no need for
| yet another GCC build. It is not very difficult to build KDE with
| GCC.
|

That is no point...
Which is the kde version of the companion CD? Check it...
Companion cds arent released with every kde release, they dont use to
release companion cds more than twice a year...
Why do I need to search on the net if I can download the packages from
the official site? Most of these releases arent maintained, and only
sporadical.

About the gcc point, looks like your mind is little bit closed, because
gcc opens a huge of possibilities that SunCC pro doesnt have, basically
~ due to its closed licenses, with gcc we can compile sparc binaries
distributed trought many boxes with diferent OSs and archs using cross
compilers, we plan to use distcc for next releases, so our x86 linux
boxes and eaven PPC boxes with MacOSx would contribute on the compiling
to the sparc box.

| The point of building KDE with the Sun compilers is to show KDE, and
| Solaris, at their best. And because it is a very interesting project
| to work on, from a software engineering perspective. I don't believe
| that either of these two reasons apply when building with GCC. It's
| certainly not what i set out to do.
|

Well, as our goals seems to be totally different, and both of us were
invited to work for KDE as contributors, we should agree in many terms,
such as release policy.

Please let us know something about, because we dont want this to become
a flame.

Sergio and Jaime.

--
Sergio Rodriguez de Guzman       -o)         Core Networks - Sistemas
~                                  /\
srodriguez <at> corenetworks.es       _\_v        http://www.corenetworks.es

------------------------------------------------------------------------------
Seducimos valiéndonos de mentiras y pretendemos ser amados por nosotros
mismos.
		-- Paul Geraldy. (1855-1954) Escritor francés.
Attachment (smime.p7s): application/x-pkcs7-signature, 3966 bytes
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
Matthew Day | 1 Oct 2004 15:45
Picon

Re: Re: KDE, Solaris, GCC, etc ...

As i understand it we all agreed the stefen would lead this project, and
I for one am happy to see that continue, and like the idea of the
release being built with suncc rather then gcc, which last time i looked
didn't have nearly as good sparc optimisation..  I'm not a coder so i
could well be wrong..

I like what the blastwave folks are doing, but see no value in double up
on efforts, even more so when Stefen has a clear history with releasing
KDE for solaris, and frankly find it rude that you would try and
dislodge him.

surely there are other packages you could work on.. get me kb3 or smb4k
working..

--Matt

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Jaime Peñalba | 1 Oct 2004 17:03
Picon

Re: Re: KDE, Solaris, GCC, etc ...

Matthew Day wrote:

>As i understand it we all agreed the stefen would lead this project, and
>I for one am happy to see that continue, and like the idea of the
>release being built with suncc rather then gcc, which last time i looked
>didn't have nearly as good sparc optimisation..  I'm not a coder so i
>could well be wrong..
>  
>
No coments....

>I like what the blastwave folks are doing, but see no value in double up
>on efforts, even more so when Stefen has a clear history with releasing
>KDE for solaris, and frankly find it rude that you would try and
>dislodge him.
>
>surely there are other packages you could work on.. get me kb3 or smb4k
>working..
>
>--Matt
>  
>
This starts to be boring, so we wouldnt spend any more time, until a 
policy is defined, either the current policy will be aplied.

>___________________________________________________
>This message is from the kde-solaris mailing list.
>Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
>Archives: http://lists.kde.org/.
>More info: http://www.kde.org/faq.html.
>  
>

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Lars Tunkrans | 1 Oct 2004 20:19

Re: Re: KDE, Solaris, GCC, etc ...

Sergio Rodriguez de Guzman Martinez wrote:

> 
> We built kde 3.1.5 and 3.2.1 for our own purpose as your 3.1.4 seemed to
> work too slow on our machines. The performance was notably increased, so
> we wanted to share it with the official site. 

I built KDE  3.0, 3.1 and 3.2   with GCC 3.2  and Gcc 3.3 on SPARC/Solaris too. And I
have only had 5 days education in C programming. ( 17 years ago  :-) )
AnyOne familiar with Unix , the Make-Process and a rudimetary knowledge
of C and C++ can build KDE with GCC.

Stefans Builds are done for Generic UltraSparc  as I understand it.  Even If I am
running on an UltraSparc 3 workstation and almost certainly would get 25% better performance
if the code was made with CXXFLAGS xtarget=ultra3 and utilize the branchprediction hardware
on the US3 chip, it's not a good idea.   To Make a Port per chiptype would probably confuse
  a lot of people and make maintaining it a nightmare.
SUN themselves are only now dropping support for UltraSparc 1  from Solaris 10

> 
> That is no point...
> Which is the kde version of the companion CD? Check it...
> Companion cds arent released with every kde release, they dont use to
> release companion cds more than twice a year...

The last two years SUN has made 3 releases per year of the whole Solaris
Package including the SW Companion, The latest Companion CD from 09/04  still
contains KDE 3.1.1 , so its very out of date by now.

//Lars

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Stefan Teleman | 2 Oct 2004 01:02
Picon

Re: Re: KDE, Solaris, GCC, etc ...

Please stop posting these unsubstantiated rumors about the Sun 
compilers and licensing issues w/r/t Open Source. Sun has never, 
*EVER* attached any restrictions on using their compilers for 
building Open Source software. This kind of garbage gossip belongs on 
Slashdot and not on this list.

Please stop making personal comments about my mind, my .signature or 
whatever else happens not to strike your fancy at any given time. 
This list is about KDE, Solaris and issues pertaining to such.

--Stefan

-----

On Friday 01 October 2004 09:31, Sergio Rodriguez de Guzman Martinez 
wrote:
> About the gcc point, looks like your mind is little bit closed,
> because gcc opens a huge of possibilities that SunCC pro doesnt
> have, basically ~ due to its closed licenses
--

-- 
Stefan Teleman          'Nobody Expects the Spanish Inquisition'
steleman <at> nyc.rr.com                          -Monty Python

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

Eva Brucherseifer | 2 Oct 2004 13:07
Picon
Favicon

Re: Re: KDE, Solaris, GCC, etc ...

Hi Sergio, Jaime and Stefan,

since I founded this kde-solaris list back in 2001 we always had users here 
asking for gcc packages as well as asking for Sun Forte packages. Also always 
people came up with questions when compiling using those compiliers. Of 
course Sun Forte wasn't an option a long time as nobody went the long way of 
porting KDE to this compiler. 

Today we have both packages available and I am very glad about this. I really 
want to thank the three of you for putting your valuable time into KDE! 
As Solaris installations are usually very hetergenous there are also users for 
both types of packages. Therefore I don't see why one package should be more 
important than the other. There are both important. gcc are usually faster 
available than suncc packages, but suncc packages usually have better 
performance. 

KDE does NOT have any policy to have only ONE type of package per platform. I 
case anybody told you, this is wrong - I even checked back with the current 
release maintainer in order to be sure. Therefore I'd love to see both 
package also in the future. You both have your users. Just name your packages 
solaris-gcc and solaris-suncc or use directories like solaris/gcc and 
solaris/suncc. 

Furthermore I'd like to invite Sergio and Jaime to get even more involved with 
this mailinglist. We have many users here who use the gcc packages and who 
have questions. There are also people here compiling KDE using gcc themselves 
and you could be a great help here. This is what this forum is for. 
This is the advantage of having long-term contributers as packagers - they 
know the system and caveats very well and they don't just disappear :-)

And both of you: There are also solaris bugs filed in the kde bugs database 
(http://bugs.kde.org/simple_search.cgi?id=solaris). You both know the system 
better then anyone else. Why not help the KDE developers (most of them don't 
really know the platform) to fix this? Why don't you work to gether to make 
KDE work perfectly on Solaris? Integrate your patches in CVS HEAD, make it 
work. 

There is no reason to fight against each other. The contributions of both of 
you are very much appreciated in KDE! 

Greetings,
eva

Am Freitag, 1. Oktober 2004 15:31 schrieb Sergio Rodriguez de Guzman Martinez:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stefan Teleman wrote:
> | And now for a litttle bit of history: when i set out to work on KDE on
> | Solaris, at the beginning of 2003, it was agreed, on this list, that
> | i will port, build and maintain KDE for Solaris with the Sun
> | compilers. If i remember correctly, a vote was taken to this effect,
> | by the members of this list.
>
> We built kde 3.1.5 and 3.2.1 for our own purpose as your 3.1.4 seemed to
> work too slow on our machines. The performance was notably increased, so
> we wanted to share it with the official site. The sysadmin of kde told
> us if we wanted to package the 3.2.2 version and continue releasing the
> next versions.
>
> | There is no point for me, nor do i have any interest, in building KDE
> | on Solaris with GCC. There is no point because it's been done
> | already, by many people, and because Sun provides KDE built with GCC
> | on their Companion CD. There are many other places on the 'Net where
> | anyone can download KDE on Solaris built with GCC. I see no need for
> | yet another GCC build. It is not very difficult to build KDE with
> | GCC.
>
> That is no point...
> Which is the kde version of the companion CD? Check it...
> Companion cds arent released with every kde release, they dont use to
> release companion cds more than twice a year...
> Why do I need to search on the net if I can download the packages from
> the official site? Most of these releases arent maintained, and only
> sporadical.
>
> About the gcc point, looks like your mind is little bit closed, because
> gcc opens a huge of possibilities that SunCC pro doesnt have, basically
> ~ due to its closed licenses, with gcc we can compile sparc binaries
> distributed trought many boxes with diferent OSs and archs using cross
> compilers, we plan to use distcc for next releases, so our x86 linux
> boxes and eaven PPC boxes with MacOSx would contribute on the compiling
> to the sparc box.
>
> | The point of building KDE with the Sun compilers is to show KDE, and
> | Solaris, at their best. And because it is a very interesting project
> | to work on, from a software engineering perspective. I don't believe
> | that either of these two reasons apply when building with GCC. It's
> | certainly not what i set out to do.
>
> Well, as our goals seems to be totally different, and both of us were
> invited to work for KDE as contributors, we should agree in many terms,
> such as release policy.
>
> Please let us know something about, because we dont want this to become
> a flame.
>
>
> Sergio and Jaime.
>
>
> - --
> Sergio Rodriguez de Guzman       -o)         Core Networks - Sistemas
> ~                                  /\
> srodriguez <at> corenetworks.es       _\_v        http://www.corenetworks.es
> -
> ---------------------------------------------------------------------------
>--- Seducimos valiéndonos de mentiras y pretendemos ser amados por nosotros
> mismos.
> 		-- Paul Geraldy. (1855-1954) Escritor francés.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBXVxItPPw0AkgUwYRAlm2AJ0XuvDTIvd1b/YAbw3HPGQC7BMFWwCeJ2nW
> quC2lYCViRgr2lLB1/F8A1E=
> =80UT
> -----END PGP SIGNATURE-----

-- 
-----------------------------------------
basysKom
Ingenieurbüro Brucherseifer und Ackermann GbR
IT System Kompetenz
-----------------------------------------
Dipl.-Ing. Eva Brucherseifer
Karlstr. 45
64283 Darmstadt
Fon: 06151-3969961   Fax: 06151-3969736
Mobil: 0170-5533642
eva.brucherseifer <at> basyskom.de
www.basyskom.de
-----------------------------------------
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

ken mays | 2 Oct 2004 16:03
Picon
Favicon

Re: kde-solaris Digest, Vol 19, Issue 2

My point is only in the documentation of processes and procedures used to port/compile/package KDE 3.3.0 on Solaris platforms. Debian does this with their QA program, so it would be nice to see it done elsewhere.

Blastwave has their standards and most of their packages is optimized for UltraSPARC2 and higher (or the sun4u platforms). Sun dropped support for the sun4m platforms. I have a SPARCstation 5 using Solaris 8 so I can test any KDE build with GCC or Sun Studio. I see NO problem in supporting users using sun4m platforms with a copy of KDE 3.3.0.

I hope we just think of a customer base of people wanting a copy of KDE 3.3.0 built with Sun Studio and GCC3 since we have a C++ ABI issue today. Also, we have to consider distributors having their way of packaging things and team of people doing it. My point is on consistent documentation of porting KDE 3.3.x to Solaris - not on compiler choices. Also, that we support KDE 3.2.3/3.3.0 on Solaris x86 just as well as we do on Solaris SPARC - or the issues involved in doing that (Mesa3D/Java3D for OpenGL).

I appreciate that Stefan, Jaime, and Sergio as well as others are porting KDE 3.3.0 to Solaris. But, I hope we know that one size doesn't fit all here. I can work with anyone who just wants to compile the code in the way I can repackage them for Blastwave distribution if they want to maintain the Sun Studio versions or GCC versions (just build your code to point to /opt/csw/lib and /opt/csw/kde-gcc/lib (GCC3) for libraries) and read the Blastwave Standards page. I can focus on Solaris x86 efforts and Solaris 10 QA testing if that helps anyone out on dedicated resources. 

Ken Mays - Earthlink, Inc. : KDE maintainer/supporter at Blastwave.org

 

Do you Yahoo!?
vote.yahoo.com - Register online to vote today!
___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
Stefan Teleman | 2 Oct 2004 18:45
Picon

Re: Re: KDE, Solaris, GCC, etc ...

OK.

So, (Don Jaime && Don Sergio):

Can we agree to the following:

Forte build KDE goes into:

<KDE 
release.major.minor>/contrib/Solaris/FORTE/≤Solaris.version.number>/<binary 
release tree>

and GCC build KDE goes into:

<KDE 
release.major.minor>/contrib/Solaris/GCC/≤Solaris.version.number>/<binary 
release tree>

and the same idea for KOffice (KOffice has its own binary release tree 
structure which is separate from core KDE).

There is a *lot* of work to be done for KDE on Solaris. I hope this 
entire little thunderstorm is soon forgotten.

If either of you, (Don Jaime || Don Sergio) would email me privately, 
there are a certain things we should talk about and make plans for. 
Eva knows what these are. :-)

If you can't get through RoadRunner spam filters, you can email me at: 
stefan|DOT|teleman|AT|gmail|DOT|com.

A big Thank you to Eva for your intervention. :-)

Peace On Earth.

--Stefan

On Saturday 02 October 2004 07:07, Eva Brucherseifer wrote:
> Hi Sergio, Jaime and Stefan,
>
> since I founded this kde-solaris list back in 2001 we always had
> users here asking for gcc packages as well as asking for Sun Forte
> packages. Also always people came up with questions when compiling
> using those compiliers. Of course Sun Forte wasn't an option a long
> time as nobody went the long way of porting KDE to this compiler.
>
> Today we have both packages available and I am very glad about
> this. I really want to thank the three of you for putting your
> valuable time into KDE! As Solaris installations are usually very
> hetergenous there are also users for both types of packages.
> Therefore I don't see why one package should be more important than
> the other. There are both important. gcc are usually faster
> available than suncc packages, but suncc packages usually have
> better performance.
>
> KDE does NOT have any policy to have only ONE type of package per
> platform. I case anybody told you, this is wrong - I even checked
> back with the current release maintainer in order to be sure.
> Therefore I'd love to see both package also in the future. You both
> have your users. Just name your packages solaris-gcc and
> solaris-suncc or use directories like solaris/gcc and
> solaris/suncc.
>
> Furthermore I'd like to invite Sergio and Jaime to get even more
> involved with this mailinglist. We have many users here who use the
> gcc packages and who have questions. There are also people here
> compiling KDE using gcc themselves and you could be a great help
> here. This is what this forum is for. This is the advantage of
> having long-term contributers as packagers - they know the system
> and caveats very well and they don't just disappear :-)
>
> And both of you: There are also solaris bugs filed in the kde bugs
> database (http://bugs.kde.org/simple_search.cgi?id=solaris). You
> both know the system better then anyone else. Why not help the KDE
> developers (most of them don't really know the platform) to fix
> this? Why don't you work to gether to make KDE work perfectly on
> Solaris? Integrate your patches in CVS HEAD, make it work.
>
> There is no reason to fight against each other. The contributions
> of both of you are very much appreciated in KDE!
>
> Greetings,
> eva
>
> Am Freitag, 1. Oktober 2004 15:31 schrieb Sergio Rodriguez de Guzman 
Martinez:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Stefan Teleman wrote:
> > | And now for a litttle bit of history: when i set out to work on
> > | KDE on Solaris, at the beginning of 2003, it was agreed, on
> > | this list, that i will port, build and maintain KDE for Solaris
> > | with the Sun compilers. If i remember correctly, a vote was
> > | taken to this effect, by the members of this list.
> >
> > We built kde 3.1.5 and 3.2.1 for our own purpose as your 3.1.4
> > seemed to work too slow on our machines. The performance was
> > notably increased, so we wanted to share it with the official
> > site. The sysadmin of kde told us if we wanted to package the
> > 3.2.2 version and continue releasing the next versions.
> >
> > | There is no point for me, nor do i have any interest, in
> > | building KDE on Solaris with GCC. There is no point because
> > | it's been done already, by many people, and because Sun
> > | provides KDE built with GCC on their Companion CD. There are
> > | many other places on the 'Net where anyone can download KDE on
> > | Solaris built with GCC. I see no need for yet another GCC
> > | build. It is not very difficult to build KDE with GCC.
> >
> > That is no point...
> > Which is the kde version of the companion CD? Check it...
> > Companion cds arent released with every kde release, they dont
> > use to release companion cds more than twice a year...
> > Why do I need to search on the net if I can download the packages
> > from the official site? Most of these releases arent maintained,
> > and only sporadical.
> >
> > About the gcc point, looks like your mind is little bit closed,
> > because gcc opens a huge of possibilities that SunCC pro doesnt
> > have, basically ~ due to its closed licenses, with gcc we can
> > compile sparc binaries distributed trought many boxes with
> > diferent OSs and archs using cross compilers, we plan to use
> > distcc for next releases, so our x86 linux boxes and eaven PPC
> > boxes with MacOSx would contribute on the compiling to the sparc
> > box.
> >
> > | The point of building KDE with the Sun compilers is to show
> > | KDE, and Solaris, at their best. And because it is a very
> > | interesting project to work on, from a software engineering
> > | perspective. I don't believe that either of these two reasons
> > | apply when building with GCC. It's certainly not what i set out
> > | to do.
> >
> > Well, as our goals seems to be totally different, and both of us
> > were invited to work for KDE as contributors, we should agree in
> > many terms, such as release policy.
> >
> > Please let us know something about, because we dont want this to
> > become a flame.
> >
> >
> > Sergio and Jaime.
> >
> >
> > - --
> > Sergio Rodriguez de Guzman       -o)         Core Networks -
> > Sistemas ~                                  /\
> > srodriguez <at> corenetworks.es       _\_v       
> > http://www.corenetworks.es -
> > -----------------------------------------------------------------
> >---------- --- Seducimos valiéndonos de mentiras y pretendemos ser
> > amados por nosotros mismos.
> > 		-- Paul Geraldy. (1855-1954) Escritor francés.
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.5 (GNU/Linux)
> > Comment: Using GnuPG with Thunderbird -
> > http://enigmail.mozdev.org
> >
> > iD8DBQFBXVxItPPw0AkgUwYRAlm2AJ0XuvDTIvd1b/YAbw3HPGQC7BMFWwCeJ2nW
> > quC2lYCViRgr2lLB1/F8A1E=
> > =80UT
> > -----END PGP SIGNATURE-----

--

-- 
Stefan Teleman          'Nobody Expects the Spanish Inquisition'
steleman <at> nyc.rr.com                          -Monty Python

___________________________________________________
This message is from the kde-solaris mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-solaris.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


Gmane