Summary: | dev-java/xerces-2.7.1 fails / xml-commons-external-1.3 not found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wulf Krueger (RETIRED) <philantrop> |
Component: | New packages | Assignee: | Java team <java> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | ebuild --debug ... install output |
Description
Wulf Krueger (RETIRED)
2006-07-06 14:17:46 UTC
Works fine for me with these versions of xerces and xml-commons-external. Could you try remering xml-commons-external? Perhaps something happened to its installation at some point... I've successfully re-emerged xml-commons-external several times already. Unfortunately, that didn't help. I've now had a look at java-pkg_jar-from() in the java-pkg eclass: "java-config --classpath=xml-commons-external-1.3" shows "/usr/share/xml-commons-external-1.3/lib/xml-apis.jar" But the whole "lib" subdirectory is missing. My first theory now was that emerging it fails even though it explicitly states otherwise: jar: [echo] Jarring ./build/xml-apis.jar from ./build/classes [mkdir] Created dir: /var/tmp/portage/xml-commons-external-1.3.02/work/xml-commons-external-1.3.02/build/classes/license [copy] Copying 7 files to /var/tmp/portage/xml-commons-external-1.3.02/work/xml-commons-external-1.3.02/build/classes/license [jar] Building jar: /var/tmp/portage/xml-commons-external-1.3.02/work/xml-commons-external-1.3.02/build/xml-apis.jar BUILD SUCCESSFUL Total time: 5 seconds >>> Source compiled. An "ebuild ... compile" creates it, though: ls -l /var/tmp/portage/xml-commons-external-1.3.02/work/xml-commons-external-1.3.02/build/xml-apis.jar -rw-r--r-- 1 root root 193558 7. Jul 06:48 /var/tmp/portage/xml-commons-external-1.3.02/work/xml-commons-external-1.3.02/build/xml-apis.jar Running "ebuild ... install" successfully creates the image structure, copies the docs and package.env - but NOT xml-apis.jar which is still fine in the build directory. I've run "ebuild --debug /usr/portage/dev-java/xml-commons-external/xml-commons-external-1.3.02.ebuild install" now to get a log for you as the problem obviously occurs in java-pkg_dojar in src_install(). I will attach the log as a text file now as it is rather huge. Should attaching it fail for any reason, you can get it at: http://www.mailstation.de/xml-commons-external-1.3.02.ebuild.debug I didn't spot anything unusual in it but that doesn't mean much. :) I won't "fix" this by copying the jar myself so that we can find out what the reason for this is. Created attachment 91091 [details]
ebuild --debug ... install output
Same problem with xml-commons-resolver. And xerces itself, too. All three show the same symptoms I described. In contrast to that commons-beanutils works fine - it uses the java-2 eclasses. java-check-environment shows no problems with either java-1 or java-2. java-1.5-fixer congratulates me for my sanity (which I consider to be cynical currently ;) ). Is there anything else I can do to help? I've now removed everything Java and tried reinstalling the needed stuff from scratch without confcache, ccache and everything else that might (or might not) influence the build process. I've deleted all eclasses and re-synched to make sure there's no bit rot or whatever. Nothing helped so far. Does it still happen if you sync and update anything and run java-check-environment to find any stale overlays that could interfer? Sorry, I forgot about this bug during those two months. After battling with Java for two more weeks or so I got all of these problems fixed by temporarily modifying some eclasses. I guess it was a temporary glitch in the new Java system because for testing I had removed all overlays, I sync daily, java-1.5-fixer and java-check-environment found no problems. |