public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeff Cranmer <jeff@lotussevencars.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Plasma-runtime compilation problems
Date: Wed, 10 Aug 2011 20:14:25 -0400	[thread overview]
Message-ID: <1313021665.8574.11.camel@laptop.limeyworld> (raw)
In-Reply-To: <j1v3h7$req$1@dough.gmane.org>

On Wed, 2011-08-10 at 16:16 -0700, walt wrote:
> On 08/10/2011 03:04 PM, Michael Schreckenbauer wrote:
> > Hi,
> > 
> > Am Mittwoch, 10. August 2011, 14:40:31 schrieb walt:
> >> On 08/09/2011 08:34 PM, Jeff Cranmer wrote:
> >>> Hi all,
> >>>
> >>> I'm trying to upgrade kde from 4.4 to 4.6, and I've run into a problem.
> >>>
> >>> Plasma-runtime-4.6.3 is failing.  The error appears to be
> >>> redefinition of 'struct QMetaTypeID<Plasma::Service*>'
> >>
> >> I don't use kde so I can't be specific, but usually a redefinition is
> >> just a warning -- unless the package is compiled with the -Wall flag or
> >> equivalent.
> 
> (Of course I meant -Werror, sorry.)
> 
> > No, this is plain wrong. Redefinition of a struct is an error in C and C++
> > 
> > ~$cat foo.c
> > struct foo {
> >         int i;
> > };
> > 
> > struct foo {
> >         char* v;
> > };
> > 
> > ~$gcc foo.c -o foo
> > foo.c:5:8: error: redefinition of 'struct foo'
> > foo.c:1:8: note: originally defined here
> 
> Hm.  I know I've seen compiler redefinition messages thousands of times
> over the years.  Is it really possible that all of those thousands were
> errors instead of warnings?  If that's true then I've wasted a lot more
> time tracking them down than I care to think about :)
> 
> 
I've seen lots of compiler warnings in the past.  This one, however, was
flagged as an 'Error', not as a warning.  It was the last message before
the compile failed, so I think it's reasonable to assume that therein
lies the problem?

I have emerged all system files, as well as a lot of the world files
that are currently out of date.  This particular compilation failure
happened late in an emerge -NDuav kdebase-meta, as the first part of the
upgrade from kde4.4 to kde4.6

Running revdep-rebuild following the emerge didn't help.  I still have
some world files that are out of date, but all of those are allegedly
not deep dependencies of kdebase-eta.  Last time I tried to do a full
emerge -NDuav world, however, I was then unable to operate my HDPVR
unit, as it suffered a lot of usb failures.  I had to recover my system
from an earlier clonezila backup, so now I'm trying to sneak up on the
problem by doing as little as possible each emerge, then checking
everything works and running another OS clone before continuing.

Unfortunately, kde is now broken, so I'm operating my mythtv interface
via gnome while I attempt to recover kde.  It's probable that the fault
lies in one of the other packages within world that are still to be
upgraded, but it would be nice to get some clues as to which one is the
culprit, so I can continue to inch up on whatever is breaking my HDPVR
based mythtv.

Jeff





  reply	other threads:[~2011-08-11  0:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  3:34 [gentoo-user] Plasma-runtime compilation problems Jeff Cranmer
2011-08-10 21:40 ` [gentoo-user] " walt
2011-08-10 22:04   ` Michael Schreckenbauer
2011-08-10 23:16     ` walt
2011-08-11  0:14       ` Jeff Cranmer [this message]
2011-08-11  0:55         ` Dale
2011-08-20 19:21           ` Jeff Cranmer
2011-08-21 18:55             ` walt
2011-08-24  0:28               ` Jeff Cranmer
2011-08-24  8:05                 ` Yohan Pereira
2011-08-24 21:12                   ` walt
2011-08-24 21:26                     ` Michael Schreckenbauer
2011-08-24 21:27                     ` Alex Schuster
2011-08-24 21:43                       ` Michael Schreckenbauer
2011-08-24 21:55                         ` Michael Schreckenbauer
2011-08-24 21:44                     ` Meik Frischke
2011-08-11  8:31       ` Michael Schreckenbauer
2011-08-12 19:22         ` walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1313021665.8574.11.camel@laptop.limeyworld \
    --to=jeff@lotussevencars.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox