From: Michael Schreckenbauer <grimlog@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Plasma-runtime compilation problems
Date: Thu, 11 Aug 2011 10:31:35 +0200 [thread overview]
Message-ID: <2380316.dSHcnf9Jls@pc> (raw)
In-Reply-To: <j1v3h7$req$1@dough.gmane.org>
Hi Walt,
Am Mittwoch, 10. August 2011, 16:16:50 schrieb walt:
> 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 prob.
> > 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 :)
struct redefinition is always an error.
Maybe what you saw as a warning was some kind of macro redefined.
~ $ cat bar.c
#define BAR 0
#define BAR 1
int main()
{
}
~$gcc bar.c -o bar
bar.c:2:0: warning: "BAR" redefined
bar.c:1:0: note: this is the location of the previous definition
Note the different wording in the message.
Regards,
Michael
next prev parent reply other threads:[~2011-08-11 8:33 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
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 [this message]
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=2380316.dSHcnf9Jls@pc \
--to=grimlog@gmx.de \
--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