public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Announce: KDE 3.0.1 20020604 (3.0.x snapshot) available
Date: Sat, 08 Jun 2002 18:52:00 +0300	[thread overview]
Message-ID: <200206081852.01082.danarmak@gentoo.org> (raw)
In-Reply-To: <200206081834.40612.kikov@fco-gimeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 08 June 2002 19:34, Francisco Gimeno wrote:
> Hi!!
>
> > Hello everyone,
> > I'm now unmasking a new set of KDE ebuilds, version 3.0.1.20020604. This
> > is the 3.0.1 release, patched to the 20020604 (i.e. June 4th) state of
> > the kde cvs's KDE_3_0 branch. In other words, this is the 3.0 release
> > with all the 3.0.1 bugfixes and then some. It contains no new features
> > from the kde cvs head, only new bugfixes, so it's ultra-stable. Enjoy!
>
> YEAAAHHH. Thx a lot :]
>
> Btw, I have a problem compiling KDEMULTIMEDIA... if you knew ;)
> -----
> {standard input}:9096: Error: symbol `rgb2y_32' is already defined
> {standard input}:9190: Error: symbol `rgb2yuv32_422' is already defined
> {standard input}:9350: Error: symbol `rgb2y_32' is already defined
> {standard input}:9444: Error: symbol `rgb2yuv32_422' is already defined
> {standard input}:9604: Error: symbol `rgb2y_32' is already defined
> {standard input}:9711: Error: symbol `rgb2yuv32_422' is already defined
> {standard input}:9872: Error: symbol `rgb2y_32' is already defined
> {standard input}:10131: Error: symbol `rgb2yuv24_422' is already defined
> {standard input}:10285: Error: symbol `rgb2yuv32_422' is already defined
> {standard input}:10458: Error: symbol `rgb2y_24' is already defined
> {standard input}:10542: Error: symbol `rgb2y_32' is already defined
> make[6]: *** [libdivxutil_dither_la.all_cpp.lo] Error 1
> make[6]: Leaving directory
> `/var/tmp/portage/kdemultimedia-3.0.1.20020604/work/kdemultimedia-3.0.1/mpe
>glib/lib/util/render/dither2YUV' make[5]: *** [all-recursive] Error 1
> ----
> I tried to unmerging div4linux.
> I'm using the GCC-3.1 profile...

I'm not one of our gcc 3.1 testers (yet :-); I know that other people have 
seen this, fex lostlogic (I think) - try to talk to him on irc perhaps. Since 
it's a known problem it should be resolved at some point.

>
> and... this all :]
> aps... another question, I post a bug:
> http://bugs.gentoo.org/show_bug.cgi?id=3504

Grabbed and responded.

>
> Thx a lot for your effort! It's really great :]
>
> Slt: KikoV
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev

- -- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9AighUI2RQ41fiVERAkcqAJ0YFwLTqRDbRKCoNwWZOx1RskY3xgCffNou
pfsYr5gTIijIjPomBHLoexI=
=Htqb
-----END PGP SIGNATURE-----



  reply	other threads:[~2002-06-08 16:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-06 20:02 [gentoo-dev] Announce: KDE 3.0.1 20020604 (3.0.x snapshot) available Dan Armak
2002-06-08 16:34 ` Francisco Gimeno
2002-06-08 15:52   ` Dan Armak [this message]
2002-06-08 17:15     ` Francisco Gimeno
2002-06-08 17:20   ` Sagie Sokolov

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=200206081852.01082.danarmak@gentoo.org \
    --to=danarmak@gentoo.org \
    --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