Works fine on an Ultra 10 Reproducible: Always Steps to Reproduce: 1. 2. 3.
jam-2.5-r2 has a ~sparc keyword, is there a particular reason you want one in jam-2.5?
No, this is just a request for jam to be tagged as stable. I use it as my primary build tool on x86 and sparc and I haven't encountered any bugs in it yet.
Tommorow I'll be taking care of bug #103893, which fixes a rather important bug. I want to give at least a week after that to verify nothing else is funky, then I'll re-assign to sparc for stable marking, and look at getting it x86 stable myself.
Making this a target for all arches. Please note the following while I wait a week to verify any strange user bugs: Ok, patches applied and did the following: emerge -pv crystalspace cel lincity-ng trigger netpanzer glest emerge crystalspace cel lincity-ng trigger netpanzer These are a list of all packages that depend on dev-util/jam. I excluded glest because it's not stable marked. Please be sure to verify these compile on your arch while the one week mark is in progress. Let me know if anything comes up in compiling those. If the above are not applicable for your arch, or are not keyworded, then don't worry about it :P. ppc-macos: please consider marking jam-2.5-r3 ~ppc-macos instead.
jam-2.5-r3 is already ~ppc-macos, so I guess we've got nothing to do.
amd64 and ppc were already stable
jam-2.5-r3 sparc stable.
