FS#55894 - [gdal] Could not compile u_char not defined
Attached to Project:
Community Packages
Opened by David McInnis (daavve) - Friday, 06 October 2017, 23:41 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Sunday, 12 November 2017, 20:42 GMT
Opened by David McInnis (daavve) - Friday, 06 October 2017, 23:41 GMT
Last edited by Jaroslav Lichtblau (Dragonlord) - Sunday, 12 November 2017, 20:42 GMT
|
Details
When Compiling gdal-2.2.1-7 I get the following error:
----------------------------------------------------------------------------------------- In file included from /usr/include/jasper/jasper.h:68:0, from jpeg2000_vsil_io.h:33, from jpeg2000_vsil_io.cpp:76: jpeg2000_vsil_io.cpp: In function 'void JPEG2000_VSIL_jas_stream_initbuf(jas_stream_t*, int, char*, int)': jpeg2000_vsil_io.cpp:210:41: error: 'uchar' was not declared in this scope stream->bufbase_ = JAS_CAST(uchar *, buf); ^ jpeg2000_vsil_io.cpp:210:41: note: suggested alternative: 'u_char' jpeg2000_vsil_io.cpp:210:32: error: expected primary-expression before ')' token stream->bufbase_ = JAS_CAST(uchar *, buf); ----------------------------------------------------------------------------------------- The following patch implements the compiler's suggestion: ----------------------------------------------------------------------------------------- +++ gdal-2.2.1/frmts/jpeg2000/jpeg2000_vsil_io.cpp 2017-10-06 14:46:45.971557273 -0700 @@ -207,7 +207,7 @@ /* The buffer must be large enough to accommodate maximum putback. */ assert(bufsize > JAS_STREAM_MAXPUTBACK); - stream->bufbase_ = JAS_CAST(uchar *, buf); + stream->bufbase_ = JAS_CAST(u_char *, buf); stream->bufsize_ = bufsize - JAS_STREAM_MAXPUTBACK; } } else { ----------------------------------------------------------------------------------------- The problem has been fixed apparently in version 2.2.2: http://trac.osgeo.org/gdal/changeset/39625/branches/2.2/gdal/frmts/jpeg2000/jpeg2000_vsil_io.cpp |
This task depends upon
Closed by Jaroslav Lichtblau (Dragonlord)
Sunday, 12 November 2017, 20:42 GMT
Reason for closing: Upstream
Additional comments about closing: The problem has been fixed apparently in version 2.2.2
Sunday, 12 November 2017, 20:42 GMT
Reason for closing: Upstream
Additional comments about closing: The problem has been fixed apparently in version 2.2.2