| Summary: | net-im/wildfire-3.1.1 fails to emerge, but 3.1.0 works | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Haplo <haplo> |
| Component: | New packages | Assignee: | Gustavo Felisberto (RETIRED) <humpback> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | hardened, java, mike, net-im |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Other | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Haplo
2006-11-22 09:57:59 UTC
If you google for the error: http://www.google.pt/search?q=Java+HotSpot(TM)+Client+VM+warning%3A+Can't+detect+initial+thread%0Astack+location+-+find_vma+failed&ie=utf-8&oe=utf-8&rls=org.mozilla:pt-PT:official&client=firefox-a You will find many messages and they are of two kinds: 1- Lack of permissions to access the /proc filesystem 2- Net/FreeBSD user running linux emulation witought having /proc from linux You are running the hardened profile so I guess the problem is there. But you say that 3.1.0 worked, so lets try one thing. Open the ebuild and find the line: eant -f build/build.xml wildfire plugins plugins-dev $(use_doc) from here remove plugins-dev so that the line looks like: eant -f build/build.xml wildfire plugins $(use_doc) then run: ebuild wildfire-3.1.1.ebuild digest and try to re-emerge. If that fixes please report back. That unfortunately did not fix it: >>> Emerging (1 of 1) net-im/wildfire-3.1.1 to / * wildfire_src_3_1_1.tar.gz MD5 ;-) ... [ ok ] * wildfire_src_3_1_1.tar.gz RMD160 ;-) ... [ ok ] * wildfire_src_3_1_1.tar.gz SHA1 ;-) ... [ ok ] * wildfire_src_3_1_1.tar.gz SHA256 ;-) ... [ ok ] * wildfire_src_3_1_1.tar.gz size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking wildfire_src_3_1_1.tar.gz ;-) ... [ ok ] * This is an upgrade * Using: sun-jdk-1.5 >>> Unpacking source... >>> Unpacking wildfire_src_3_1_1.tar.gz to /var/tmp/portage/wildfire-3.1.1/work >>> Source unpacked. Rewriting ./build/build.xml >>> Compiling source in /var/tmp/portage/wildfire-3.1.1/work/wildfire_src ... Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - find_vma failed Buildfile: build/build.xml init: [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work [unjar] Expanding: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/build/lib/merge/whack.jar into /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/whack compile: [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/classes [javac] Compiling 435 source files to /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. jspc: [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc/java [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc/classes [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/webapp -jspc-impl: [java] Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location - find_vma failed [java] Java Result: 137 BUILD FAILED /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/build/build.xml:408: The following error occurred while executing this line: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/build/build.xml:434: Unable to load file: java.io.FileNotFoundException: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc/web.partial.xml (No such file or directory) Total time: 13 seconds !!! ERROR: net-im/wildfire-3.1.1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile wildfire-3.1.1.ebuild, line 55: Called eant '-f' 'build/build.xml' 'wildfire' 'plugins' java-utils-2.eclass, line 1345: Called die !!! eant failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08" JAVACFLAGS="-source 1.5 -target 1.5" COMPILER="javac" and of course, the output of emerge --info I'm not running BSD and I do have /proc so does that mean that portage/java are unable to access the information in /proc they need? To the hardened & java herds: This error seems to me a bit out of my league. Please advice on the correct way to fix this. Try a more recent kernel. GRsecurity used to forbid reading of all /proc/<pid>/maps and related data, to avoid an information leak that would make randomisation of process maps useless for making it harder to exploit buffer overruns. Recent GRsecurity patches permit a process to read its own data (since that information is available anyway), just forbids reading the data about other other processes. Went into 2.6.16 some time - 2.6.17-r1 is latest stable and that definitely has it. He... That was an adventure (http://www.mindstab.net/wordpress/archives/169) And unfortunately didn't work. Still the same problem >>> Source unpacked. Rewriting ./build/build.xml >>> Compiling source in /var/tmp/portage/wildfire-3.1.1/work/wildfire_src ... Buildfile: build/build.xml init: [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work [unjar] Expanding: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/build/lib/merge/whack.jar into /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/whack compile: [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/classes [javac] Compiling 435 source files to /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/classes [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. jspc: [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc/java [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc/classes [mkdir] Created dir: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/webapp -jspc-impl: [java] Java Result: 137 BUILD FAILED /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/build/build.xml:408: The following error occurred while executing this line: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/build/build.xml:434: Unable to load file: java.io.FileNotFoundException: /var/tmp/portage/wildfire-3.1.1/work/wildfire_src/work/jspc/web.partial.xml (No such file or directory) Total time: 13 seconds !!! ERROR: net-im/wildfire-3.1.1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile wildfire-3.1.1.ebuild, line 55: Called eant '-f' 'build/build.xml' 'wildfire' 'plugins' java-utils-2.eclass, line 1345: Called die !!! eant failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! When you file a bug report, please include the following information: GENTOO_VM=sun-jdk-1.5 CLASSPATH="" JAVA_HOME="/opt/sun-jdk-1.5.0.08" JAVACFLAGS="-source 1.5 -target 1.5" COMPILER="javac" and of course, the output of emerge --info Just wanted to chime in that while I never saw the "Client VM Warning", I initially did get the same "file not found" error. My output looked just like that in comment #5. I quickly remembered the sun-jdk had just been updated, as well. I did "/etc/init.d/chpax restart" and the problem disappeared. Assuming fixed as no info has been given in half an year. |
