[kde-linux] KDE-4.14.0 doesn't work

[James Tyrer]

On 09/12/2014 06:11 PM, Duncan wrote:
> James Tyrer posted on Fri, 12 Sep 2014 12:41:54 -0700 as excerpted:
>
>> On 09/11/2014 01:27 PM, Duncan wrote:
>>> James Tyrer posted on Thu, 11 Sep 2014 12:26:15 -0700 as excerpted:
>>>
>>>> I mentioned problems with KDE-4.14.0.  At start up, Plasma-Desktop
>>>> immediately crashes and will not restart. [S]ome research indicates
>>>> that Qt-4.8.6 will not run on AMD-64 bit processors.  Going back to
>>>> 4.8.4, which I still had on the system, fixed  the problem.
>>>
>>> While I'm running kde4-live, here's what plasma-desktop --version
>>> reports:
>>>
>>> Qt: 4.8.6 KDE Development Platform: 4.14.0 Plasma Desktop Shell:
>>> 4.11.11
>
>>> So kde-4.14.x and qt-4.8.6 is running fine on amd64, here. =:^)
>>> Do you have any more information on that qt-4.8.6 not running on amd64
>>> claim?  Was it qt-4.8.6 in general or only with kde?  What part of qt4
>>> (qtcore, qtwebkit, qtgui, etc) was it?
>
>> Which GCC did you use?  IF you recall, there was a problem with 4.8.4:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=450818 which was fixed.  But,
>> something appears to have gone wrong with the new version of the
>> compiler: GCC-4.9.0
>
> I never saw that bug here.  I must have been lucky and not gotten the bad
> combination of qt/plasma/gcc all at the same time.
>
>> Before with 4.8.4 it was an issue of optimization so it was a compiler
>> issue.  So, it is going to make a difference which compiler you are
>> using and which compiler options you use.
>
> But gcc version might explain it.  I've been busy enough (and gcc for
> amd64 is mature enough improvements tend to be pretty incremental anyway,
> unlike the early days of the arch, so there's not as much motivation to)
> I've not been tempting fate on masked gcc so much lately.  I do run
> ~amd64, indicating testing branch on gentoo, but due to the wide variety
> of packages gentooers build from source and the flexibility they give
> users in terms of cflags, etc, gentoo tends to take a bit longer than
> some distros to even unmask a new gcc to ~arch, let alone stable.
>
> As a result I'm still on gcc 4.8.3, with gentoo applying various patches
> both to gcc and to various packages such that it's reasonably stable by
> now.  Which as I said may well explain it.
>
I usually go ahead and update GCC because if there is a building problem 
with anything on the LFS/BLFS sites, there is a fix for it.

Now I see that GCC 4.9.1 has been released so there might have been some 
problems with the ".0" release.  So, since LFS is going to upgrade to 
that, I will try building Qt-4.8.6 with that and see if it works.  That 
will take a while even with a 4400+ processor.

-- 
James Tyrer

Linux (mostly) From Scratch


-- 
James Tyrer

Linux (mostly) From Scratch