Re: Problem compiling kdebase...
- Date: Mon, 12 May 2008 09:25:40 +0200
- From: edg72@xxxxxxx
- Subject: Re: Problem compiling kdebase...
Hi Dan,
Thanks, I upgraded to gcc 4.2.3 and now kdebase compiles. I checked the GNU site and found out that GCC 4.2 was released just about a year ago.
Requiring GCC 4.2 or higher for KDE 4.1 thus might be a bit too much. For example, Gentoo still installs GCC 4.1.2 by default since 4.2.3 is not declared stable for most architectures.
I have no clue about other distributions though...
Best Regards,
Erik
On Tuesday 06 May 2008 23:56:18 Dan Meltzer wrote:
> On 5/6/08, edg72@xxxxxxx <edg72@xxxxxxx> wrote:
> > Hi,
> >
> > When compiling kdebase (revision 804656) from trunk I get the following error:
> >
> > /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/libs/plasma/applet.h: In member function 'Plasma::Applet* Plasma::Containment::Private::addApplet(const QString&, const QVariantList&, const QRectF&, uint, bool)':
> > /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/libs/plasma/applet.h:502: error: 'Plasma::Applet::Applet(QGraphicsItem*, const QString&, uint)' is protected
> > /var/tmp/portage/kde-base/kdebase-9999.4/work/kdebase-9999.4/workspace/libs/plasma/containment.cpp:986: error: within this context
> >
> > I have this problem for a week now and I am starting to wonder whether this is a local problem or a problem in svn as I initially thought. Also on the KDE dashboard it seems kdebase compiles just fine... I already cleared my local copy and did a "svn co" to assure I really have the latest and greatest, but this did not solve the problem.
> >
> > I checked the applet.h header file and the function/method GCC complains about is really protected. I also noticed this was changed a week ago in svn because of the Plasma API review.
> >
> > Does anyone have the same problem? If not, can one of you give me a hint on what could be the cause of this? If it is a problem in svn, I will be very patient and wait until it gets fixed ;-)
>
> This is due to a bug in the gcc version you are using. It works fine
> in gcc 4.2/4.3
>
> The question of course, is is it really okay to bump the gcc versiond
> ependancy or should these go back to being public.
> >
> > Your help is really appreciated!
> >
> > Best Regards,
> > Erik
> >
> >
> > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
> >
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
>
>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<