On Tue, 10 Jun 2008 16:52:36 -0700, AGT wrote:

> KDE - talk about a work in "progress".. : <

Nowhere nearly as much so as GNOME. Slackware Linux gave up on chasing
all the varying GNOME requirements and dropped it from their distribution.
It's easy to see why Sun doesn't chase the GNOME versions.

> A pity as I rather like its look and feel compared to GNOME

I've grown accustomed to GNOME. I had a bit of a problem getting into
GNOME earlier today; the X config has changed since I replaced a 1280x1024
display with one that does 1680x1050. I could log into "Failsafe" and
started twm to fiddle with the X config. But I forgot to see if I could
get KDE to start up.

On the next login GNOME came back up without problems so I'll wait a bit
to see if KDE will actually start.

>> Exactly! Are there any CFLAGS for Studio12 which will cause the
>> compiler to overlook those errors as gcc does?
>
> "those" errors? cc has an awful lot of switches, rather well documented
> I recall that 12 is more gcc tolerant or like in some respects but the
> details I do not recall. But I do not think mplayer for example will
> build w/o some extensive fixups.

mplayer is something of an oddball. Its configure script looks like one
created with GNU autoconf but it's not. Only gmake can be used and forget
about trying to use Studio12.