trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: April 2012

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

From: Darrell Anderson <humanreadable@...>
Date: Thu, 12 Apr 2012 12:56:35 -0700 (PDT)
>   Just completed another complete rebuild of TDE with
> gcc47 with NO makeflags at all (just to make sure building wasn't an issue) knemo shows
> the exact same behavior - no modules found. kcontrol opens and lists the
> main headings on the left, but it is completely empty:
> 
> http://www.3111skyline.com/dl/dt/trinity/ss/kcontrol-empty.jpg
> 
>   I can't figure out what this could be. Everything
> that built, built without crashing. The only build failures I had were:
> 
> tde-kipi-plugins - error: redeclaration of 'TQListViewItemIterator it'
> 
> tde-tdepim - error: redeclaration of 'TQMap<TQGuardedPtr<KMFolder>,
> int>::Iterator it'
> 
> tde-k3b - error: redeclaration of
> 'K3bAudioEditorWidget::Range* r'
> 
> digiam - still dead with libpng15 issue.
> 
>   There seems to be a common thread in the failures
> above. I have no idea how to solve redeclaration issues. The only thing I can think of
> for the current kcontrol and knemo, etc.. module failure issues is there is
> something similar going on that isn't being flagged as 'fatal' during the
> build but that is killing the modules in tdelibs nonetheless.

Looks like gcc 4.7 will require some major code cleanup. However, today I ran across this response in a forum discussion:

https://www.linuxquestions.org/questions/slackware-14/zoneminder-1-25-0-wont-build-in-slackware64-current-939357/#post4650610
Perhaps some of the 4.7 problems will be resolved by manually adding unistd.h in the preprocessor includes.

This document explains the changes in gcc 4.7:

http://gcc.gnu.org/gcc-4.7/changes.html

Somebody more experienced with compilers could help by translating that information into a wiki how-to of what types of failures to expect, what types of cures will help, and when those cures need to be explicitly defined in the build process.

Darrell