Message: previous - next
Month: April 2012

Re: [trinity-devel] plan for dealing with fixing gcc47 '-fpermissive' requirement? What's usually involved?

From: "Timothy Pearson" <kb9vqf@...>
Date: Thu, 19 Apr 2012 23:49:28 -0500
> All,
>   What is usually involved in updating the packages to get rid of the
> '-fpermissive' build flag requirement brought on by gcc47? What do you
> look for?
> Just remove '-fpermissive' and build over and over fixing along the way or
> is
> there a better way?
>   By my count, the following packages require '-fpermissive' with gcc47:
> amarok
> digikam
> kaffeine
> kipi-plugins
> kmplayer (other issues as well)
> koffice (still requires libpng15 fixes)
> krusader
> python-tqt
> rosegarden
> tdeadmin
> tdebase
> tdeedu
> tdegames
> tdegraphics
> tdepim
>   Those are just those out of the packages I have built. There are
> probably
> others as well. Any suggestions?
> --
> David C. Rankin, J.D.,P.E.

Removing the permissive flag and rebuilding is the only method that I have
used to resolve the problems in the past.  One other method MIGHT be to
build the package with the permissive flag and see if gcc gives a unique
warning message when an error has been downgraded to a warning.