Opened 13 years ago
Closed 13 years ago
#6597 closed defect (fixed)
Current JOSM broke compilation in gentoo
Reported by: | anonymous | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: | Flowzn |
Description
Buildfile: /var/tmp/portage/sci-geosciences/josm-9999/work/josm/build.xml
init:
[mkdir] Created dir: /var/tmp/portage/sci-geosciences/josm-9999/work/josm/build
[mkdir] Created dir: /var/tmp/portage/sci-geosciences/josm-9999/work/josm/dist
compile:
[javac] Compiling 124 source files to /var/tmp/portage/sci-geosciences/josm-9999/work/josm/build
[javac] /var/tmp/portage/sci-geosciences/josm-9999/work/josm/src/com/drew/metadata/exif/NikonType2MakernoteDirectory.java:152: unmappable character for encoding UTF-8
[javac] * - ?
[javac]
[javac] /var/tmp/portage/sci-geosciences/josm-9999/work/josm/src/com/drew/metadata/exif/NikonType2MakernoteDirectory.java:360: unmappable character for encoding UTF-8
[javac] * - 0100w\cH+D$$h$?5Q (D1X)
[javac]
[javac] 2 errors
Attachments (0)
Change History (6)
comment:1 by , 13 years ago
comment:2 by , 13 years ago
@anonymous: You should mention at least the josm version you are trying to compile. The build.xml should be fixed by now.
@stoecker: probably iso-8859-1, at least it compiles with that setting.
comment:3 by , 13 years ago
No, iso-8859-1 does not produce useful results for these 2 lines. Some windows charset maybe.
comment:4 by , 13 years ago
It's the live ebuild from gentoo that pulls the latest svn for installing josm on gentoo. Just hit the same problem. :(
There is one problematic non ascii character "<EE>" in two lines within NikonType2MakernoteDirectory.java:
- line 152: * - <EE>AL
- line 360: * - 0100w\cH+D$$hT$<EE>5Q (D1X)
comment:5 by , 13 years ago
Cc: | added |
---|
This are warnings normally. Why are they errors.
I wanted to fix these, but I do not know the original charset, so I was unable to convert it to UTF-8.