Closed GoogleCodeExporter closed 9 years ago
The error message in the title of this issue occurs three places in the code.
We are currently hitting the one in opj_jp2_read_header_procedure (
http://code.google.com/p/openjpeg/source/browse/trunk/src/lib/openjp2/jp2.c#1674
). Not sure if this case matches the case described in the description or if
that's one of the other two cases.
One of the jp2s impacted by the issue:
http://chroniclingamerica.loc.gov/lccn/sn83045433/1913-02-20/ed-1/seq-1.jp2
This issue is a show stopper for our use case of openjpeg. Any ideas if/when a
patch/release might happen?
Original comment by eik...@eikeon.com
on 20 Feb 2013 at 9:56
I'm now running svn revision 2299 with the patch from
https://groups.google.com/d/msg/openjpeg/PhZvwg_OjoU/9vVAiL6rt8wJ applied which
has fixed the issue I described in my previous comment.
Is it safe to assume that this patch will find its way into trunk and
eventually a 2.0.1 release?
Original comment by eik...@eikeon.com
on 8 Mar 2013 at 7:15
This issue was closed by revision r2313.
Original comment by savmick...@gmail.com
on 17 Mar 2013 at 6:16
I'm not able to test r2313 as I'm still running into the following issue while
building ever since r2301:
In file included from /Users/eikeon/Projects/openjpeg/src/bin/jp2/index.c:34:
/Users/eikeon/Projects/openjpeg/src/lib/openjp2/opj_inttypes.h:39:2: error:
unsupported platform
#error unsupported platform
I'll look to see if an issue has been opened for it so that I can test this
issue once the other issue is fixed.
Original comment by eik...@eikeon.com
on 19 Mar 2013 at 2:48
I could not find an existing issue for the build problem I mentioned in the
previous comment. So I opened an issue for it:
http://code.google.com/p/openjpeg/issues/detail?id=214
Original comment by eik...@eikeon.com
on 19 Mar 2013 at 2:57
Yep, looks like the patch made it in fine from my perspective. The test case I
wrote in my application for this issue is now passing running against trunk
(just tested with r2315).
Thanks again.
Original comment by eik...@eikeon.com
on 20 Mar 2013 at 12:45
Original issue reported on code.google.com by
mathieu.malaterre
on 15 Nov 2012 at 2:04Attachments: