this may not be a bug with this package... !!! Failed to determine VM for building. !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/log/portage/dev-java:swt-3.2.2:20070311-161519.log'. !!! When you file a bug report, please include the following information: GENTOO_VM= CLASSPATH="." JAVA_HOME="" JAVACFLAGS="-source 1.4 -target 1.4" COMPILER="" and of course, the output of emerge --info I've gone through this guide http://www.gentoo.org/doc/en/java.xml and I haven't solved this yet. It seems like I have to fix something with java for building stuff all the time. like the system isn't remembering my settings or something. anyways what else do I need to do to get this package updated. my system jdk is blackdown-jdk-1.4.2 and my generation-2 is sun-jdk-1.6 Reproducible: Always
Post the output of java-config --list-available-vms, java-check-environment and emerge --info here.
Created attachment 112975 [details] emerge --info java-config --list-available-vms The following VMs are available for generation-2: *) Blackdown JDK 1.4.2.03 [blackdown-jdk-1.4.2] 2) Sun JDK 1.6.0 [sun-jdk-1.6]
see above comment
You forgot java-check-environment output please.
(In reply to comment #4) > You forgot java-check-environment output please. > sorry. * === Java Environment Checker === * The purpose of this script is to check the sanity of your Java Environment. * We have significantly changed and improved the way Java is handled in many respects. * Please refer to http://www.gentoo.org/proj/en/java/java-upgrade.xml for details * Checking vm_environment_files ... [ ok ] * Checking user_settings ... * Running as root. Don't need to check user settings. [ ok ] * Checking generation_1_system_vm ... [ ok ] * Checking virtual_provides ... [ ok ] * Checking overlays_eclasses ... [ ok ] * Java environment is sane. Congratulations!
Please post the contents of /etc/java-config-2/build/jdk.conf and /usr/share/java-config-2/config/jdk-defaults.conf and the version of java-config installed. Also full build log would help, there should be more error messages above the "Failed to determine..."
wtf 2. this one hasn't worked for 2 weeks or more for me. maybe that fsck that ran on /var on reboot fixed something. really weird and I don't like it when 2 problems just vanish for seemingly no reason. sigh closing worksforme
Created attachment 113030 [details] dev-java:swt-3.2.2 build log /etc/java-config-2/build/jdk.conf (changed for troubleshooting) 1.6=sun-jdk 1.5=sun-jdk 1.4=blackdown-jdk other file referenced is still at defaults.
now it's not working again
caleb, I don't think your system is sane (also see Bug 170456) and you should debug your HW/filesystem/whatever else before filing other bugs that don't seem to be reproducible anywhere.
From the lo(In reply to comment #8) > Created an attachment (id=113030) [edit] > dev-java:swt-3.2.2 build log > Traceback (most recent call last): File "/usr/bin/depend-java-query", line 85, in ? (options, args) = parser.parse_args() File "/usr/lib/python2.4/optparse.py", line 1275, in parse_args stop = self._process_args(largs, rargs, values) File "/usr/lib/python2.4/optparse.py", line 1315, in _process_args self._process_long_opt(rargs, values) File "/usr/lib/python2.4/optparse.py", line 1390, in _process_long_opt option.process(opt, value, values, self) File "/usr/lib/python2.4/optparse.py", line 707, in process return self.take_action( File "/usr/lib/python2.4/optparse.py", line 726, in take_action self.callback(self, opt, value, parser, *args, **kwargs) File "/usr/bin/depend-java-query", line 49, in get_vm vm = verman.get_vm(value) File "/usr/share/java-config-2/pym/java_config/VersionManager.py", line 123, in get_vm matched_atoms = self.parse_depend(atoms) File "/usr/share/java-config-2/pym/java_config/VersionManager.py", line 56, in parse_depend from portage import flatten File "/usr/lib/portage/pym/portage.py", line 8321, in ? init_legacy_globals() File "/usr/lib/portage/pym/portage.py", line 8277, in init_legacy_globals db = create_trees(**kwargs) File "/usr/lib/portage/pym/portage.py", line 8233, in create_trees config_incrementals=portage_const.INCREMENTALS) File "/usr/lib/portage/pym/portage.py", line 1199, in __init__ allow_sourcing=True) File "/usr/lib/portage/pym/portage_util.py", line 349, in getconfig raise portage_exception.ParseError(str(e)+" in "+mycfg) portage_exception.ParseError: [Errno 13] Permission denied: '/usr/local/portage/make.conf' in /etc/make.conf Please give portage group read permission to /usr/local/portage/make.conf and reopen if that does not fix the problem.
ok jakub tell me if I'm wrong here. (knows you will) if this is the make.conf that layman sets and I source isn't this a bug caused by the layman ebuild? because if this is breaking portage ebuilds layman should correct my 077 UMASK (set in /etc/profile) and or my root:root ownership instead of installing the default and making me correct it. and correcting ownership and permissions 100% fixes the problem. these should be set by layman either at runtime or in install.
You are completely on your own when messing with default umask, don't blame layman, you did set it.
