Message: previous - next
Month: April 2012

Re: [trinity-devel] Bad News [was Re: [trinity-devel] All tde modules FAIL when built on gcc47 (kdesktop, knemo, kcontrol, etc...)]

From: /dev/ammo42 <mickeytintincolle@...>
Date: Sun, 15 Apr 2012 13:33:28 +0200
On Sat, 14 Apr 2012 16:41:55 -0700 (PDT)
Darrell Anderson <humanreadable@...> wrote:

> > I just completed a complete rebuild on gcc46 - and the
> > modules are still broken. You cannot launch kcontrol from the menu
> > any longer. The only way to open it was via konsole and 'kcontrol'
> > directly.
> > 
> > knemo no longer works - same kcm_shell issue...
> > 
> > screenshot:
> > 
> >
> > 
> > There were no build issues. In fact - great job pushing the
> > patches. The only failures I had were attempts to revert a
> > previously applied patch where I hadn't removed them from the
> > scripts yet.
> > 
> > I don't know what changed since 3/29 and today that would
> > break kcontrol, etc.. I'll leave this to you that know the code. I
> > don't know where to begin. Let me know if you would like me to run
> > some additional test and I'm happy to do it. I'm just not sure what
> > to test.
> I just built everything here on Slackware 13.1 (gcc 4.4.4). No
> noticeable problems.
> For problems like this, consider not building anything beyond the
> core packages because that minimal install provides sufficient
> evidence of what is working or breaking. I do that quite often when I
> want to test the basics. Doing similarly would save you much time as
> KControl will show most of the modules just by building
> tdelibs/tdebase. A few modules from the remaining packages will be
> missing, but you'll know right away whether KControl is broken.
> I finally created Slackware 13.37 partitions so I can start testing
> Trinity with that release (gcc 4.5.2). I intend to do likewise with
> Slackware Current (the testing system for the next official release),
> which now uses gcc 4.7. With 13.37 I can provide confirmations of
> what builds and what doesn't. Moreso with Current and gcc 4.7.
> The only kink with this plan is I can build only 13.37 or Current at
> one time. I only have two machines capable of doing this work and
> three Slackware systems to test. :( As 13.1 remains my primary
> system, my primary machine will remain tied to that. Virtual machines
> are great for usability testing but too slow for this amount of
> repetitive building.
You can also chroot into a Slackware partition and run the chrooted
system under the kernel of the host system:
(but with the apparition of KMS on modern systems, I'd rather use the X
server of the host than the one of the chroot).
> Darrell
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> trinity-devel-unsubscribe@... For additional
> commands, e-mail: trinity-devel-help@... Read
> list messages on the web archive:
> Please remember not to
> top-post: