public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: BoehmeSilvio <Boehme.Silvio@afb.de>
To: "'gentoo-dev@gentoo.org'" <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] kdeaddons-2.2.2-r1 fails
Date: Mon, 21 Jan 2002 18:07:54 +0100	[thread overview]
Message-ID: <E19CBDD9F21ED111A96A00805F0D6AE0FCFB06@AFBWNT01> (raw)

Sorry for this post, I found this also on BUGTRAQ 173.

I'll try to remerge the kdemultimedia package.

By



> -----Ursprüngliche Nachricht-----
> Von: BoehmeSilvio [mailto:Boehme.Silvio@afb.de]
> Gesendet: Montag, 21. Januar 2002 17:59
> An: gentoo-dev@gentoo.org
> Betreff: [gentoo-dev] kdeaddons-2.2.2-r1 fails
> 
> 
> Hi,
> 
> i have a problem with kdeaddons-2.2.2-r1.ebuild on two machines.
> 
> Emerge stops with:
> 
> ...
> ...
> wakeup.moc: In method 'void WakeupPrefs:: initMetaObject()':
> wakeup.moc:109: 'CModule' undeclared (first use this function)
> wakeup.moc:109: parse error before '::'
> wakeup.moc:112: confused by earlier errors, bailing out
> cpp0: output pipe has been closed
> make[3]: *** [libnoatunwakeup_la.all_cpp.lo] Error 1
> make[3]: Leaving directory
> '/var/tmp/portage/kdeaddons-2.2.2-r/work/kdeaddons-2.2.2/noatu
> n-plugins/alar
> m
> 
> 
> I get this on two different machines.
> 
> Thanks in advance,
>  
> Silvio
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
> 


             reply	other threads:[~2002-01-21 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-21 17:07 BoehmeSilvio [this message]
2002-01-21 17:12 ` [gentoo-dev] kdeaddons-2.2.2-r1 fails Dan Armak
2002-01-21 17:53   ` Lars Scheele Jensen
  -- strict thread matches above, loose matches on Subject: below --
2002-01-21 16:58 BoehmeSilvio

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=E19CBDD9F21ED111A96A00805F0D6AE0FCFB06@AFBWNT01 \
    --to=boehme.silvio@afb.de \
    --cc=gentoo-dev@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