Dieter Ries <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 02 Sep 2006 13:28:00 +0200:
> two of 600 ebuilds of my --emptytree world with gcc 4.1.1 failed, xdvik and > timidity++. here is the output : Interesting. xdvik I don't have merged, but I do timidity. I checked how long ago I merged it and it appeared to have been with gcc-4.0.2, back in January, so I remerged and it went just fine with gcc-4.1.1. However, it looks like you were using 2.13.2 while I have 2.13.2-r2 merged here (since January). I see this entry in the changelog: 26 Jun 2005; Mark Loeser <[EMAIL PROTECTED]> +files/timidity++-2.13.2-gcc4.patch, timidity++-2.13.2-r2.ebuild: GCC4 patch, thanks to <[EMAIL PROTECTED]> for the patch; bug #89933 Thus, it would appear you need -r2 to compile with gcc4. $earch timidity++ timidity++-2.13.2[0]: amd64 arm hppa ppc sparc x86 timidity++-2.13.2-r2[0]: ~amd64 ~arm ~ppc ppc64 ~sparc ~x86 So... -r2 is still keyworded unstable. With gcc-4.1.1 now stable, that's a bug. A quick look to see if it's already filed reveals: http://bugs.gentoo.org/show_bug.cgi?id=145669 If you are running a mostly stable amd64 system, try adding this specific version to package.keywords as ~amd64. If it then merges fine, test it and be sure it works, then add [EMAIL PROTECTED] to the CC list for the bug above, and add a note saying you've confirmed that it does indeed merge and work on amd64 stable. That should get it stabilized fairly fast, unless Gentoo sound team itself has issues with it going stable, and I don't see any listed and it's already stable for ppc64. It seems fine on ~amd64 here, but that's of course not the same as saying it's fine on stable, so your specific statement to that effect would be helpful. Don't forget to add your emerge --info too, so they know what USE flags you use. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
