Summary: | dev-java/joda-time-1.6 emerge can't compile zoneinfo | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rodrigo Severo <rodrigo> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gravyjunk, steven |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rodrigo Severo
2009-03-22 19:52:57 UTC
I've send a message to joda's mailing list mentioning this issue. I got the following answer from Brian O'Neill. Does it help? "The tz building code doesn't work when time zones are supported. You need to force UTC only with a system property: -Dorg.joda.time.DateTimeZone.Provider=org.joda.time.tz.UTCProvider The ant build script does the same thing." joda-time emerges just fine if /etc/localtime is a copy of either /usr/share/zoneinfo/America/Sao_Paulo or /usr/share/zoneinfo/right/America/Sao_Paulo It also emerges fine if /etc/localtime is a symlink to /usr/share/zoneinfo/America/Sao_Paulo Unfortunatelly it fails to emerge if /etc/localtime is a symlink to /usr/share/zoneinfo/right/America/Sao_Paulo I will copy this info upstream. If I get any extra info there I will report back. (In reply to comment #2) > I will copy this info upstream. If I get any extra info there I will report > back. Did you report the issue upstream? (In reply to comment #3) > Did you report the issue upstream? I believe I did but unfortunatelly I don't remember exactly the result. I think this bug can be closed as WORKSFORME. I have the same problem, and the Sao_Paolu workaround in the comments doesn't work for me. As far as setting the UTC system property, is that just setting the -D... in an ANT_OPTS variable on the emerge line, or do I need to do something else? Nevermind about comment #5. I switched my timezone to Greenwich (no offset to add / subtract) and it emerged just fine. I switched to GMT also and it worked fine. (AMD64) Does this still happen on the newest version (2.2)? (In reply to Tom Wijsman (TomWij) from comment #8) > Does this still happen on the newest version (2.2)? BUILD SUCCESSFUL Total time: 10 seconds >>> Source compiled. >>> Test phase [not enabled]: dev-java/joda-time-1.6 >>> Install joda-time-1.6 into /var/tmp/portage/dev-java/joda-time-1.6/image/ category dev-java >>> Completed installing joda-time-1.6 into /var/tmp/portage/dev-java/joda-time-1.6/image/ There's even a 2.7 version that works just as fine. package: [jar] Building jar: /var/tmp/portage/dev-java/joda-time-2.7/work/joda-time-2.7/target/joda-time-2.7.jar jar: BUILD SUCCESSFUL Total time: 9 seconds >>> Source compiled. >>> Test phase [not enabled]: dev-java/joda-time-2.7 >>> Install joda-time-2.7 into /var/tmp/portage/dev-java/joda-time-2.7/image/ category dev-java >>> Completed installing joda-time-2.7 into /var/tmp/portage/dev-java/joda-time-2.7/image/ Closing this bug. |