dev-java/kissme-classpath -jikes dev-java/avalon-phoenix -jikes dev-java/log4j -jikes dev-java/jacl -jikes dev-java/makeme -jikes dev-java/jdbc3-postgresql -jikes dev-util/eclipse-cbg-editor -jikes =dev-java/avalon-logkit-1.2 -jikes dev-java/jaxen -junit www-servers/tomcat -jikes these packages need -jikes in order to compile properly please delete the jikes use flag from them
confirmation is: strace /usr/bin/ebinfo open("/usr/share/locale/it_IT@euro/LC_MESSAGES/eb.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/it@euro/LC_MESSAGES/eb.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/it_IT/LC_MESSAGES/eb.mo", O_RDONLY) = -1 ENOENT (No such file or directory) open("/usr/share/locale/it/LC_MESSAGES/eb.mo", O_RDONLY) = -1 ENOENT (No such file or directory) write(2, "/usr/bin/ebinfo: failed to open "..., 47/usr/bin/ebinfo: failed to open a catalog file it's using nls, but seems that translated messages are not merged in
sorry, wrong post, too many tab opened. discard this comment, i'm sorry
I just looked into the packages you listed. The following are no longer in portage: * dev-java/avalon-phoenix * dev-java/kissme-classpath The following no longer have jikes flag: * =dev-java/avalon-logkit-1.2 * dev-java/jdbc3-postgresql The following are still, and I wasn't able to get to build otherwise: * dev-util/eclipse-cbg-editor The following are still affected: * dev-java/jacl * dev-java/makeme The ones still affected are dependent on bug #89711.
For the packages not currently working, I've updated in CVS to no longer use jikes. If you experience further problems with jikes, please open a new bug for each package affected.
i just synched and saw that dev-java/avalon-logkit-1.2 still have it. online cvs shows the same. what's up?
(In reply to comment #5) > i just synched and saw that dev-java/avalon-logkit-1.2 still have it. > > online cvs shows the same. what's up? Indeed, but I tested on sun-jdk-1.5 and blackdown-jdk-1.4 and both work with jikes. I do get a couple of Semantic warnings but that does not make the emerge stop.
Let's put this as NEEDINFO. Please provide information on the jdk you are using and output from the avalon-logkit-1.2 failure and REOPEN.
o yes it works for me too. now i'm retesting my list. my config is: jdk 1.5 and jikes. i know 1.5 is masked, should i fill a bug for every package not working? for example log4j doesn't work with jikes, and i saw that overlay has dropped this use flag. what should i do? report a bug for that?
(In reply to comment #8) > o yes it works for me too. > > now i'm retesting my list. > > my config is: jdk 1.5 and jikes. > i know 1.5 is masked, should i fill a bug for every package not working? > You should file bugs for the jikes use flag not working. Bugs caused by the jdk 1.5 are not our problem because it is package.masked for a very good reason. The solution is the axxo-overlay. > > for example log4j doesn't work with jikes, and i saw that overlay has dropped > this use flag. > The axxo-overlay handles compiler configuration differently. > what should i do? report a bug for that? Nope if you are talking about axxo-overlay. Take a look at /etc/java-config/compilers.conf
no i'm not using any overlay. i'll do this: wait for jdk 1.5 unmask (overlay merged) and retest all. thx for infos