[Gdal-dev] jp2kak on OSX

[Collins, Benjamin]

In Kakadu 5.1 there are two (new?) shared objcet files that are not
explicitly mentioned in the GNUMakefile in frmts/jp2kak.  These files
are:
<kdu_dir>/apps/make/jpx.o
<kdu_dir>/apps/make/kdu_tiff.o

If those file are added to the GNUMakefile you will proabaly be able to
build correctly.  I did not check the change into CVS because I'm
concerned that doing so would break gdal builds for old versions of
kakadu.

--
Ben Collins

>-----Original Message-----
>From: gdal-dev-bounces at lists.maptools.org 
>[mailto:gdal-dev-bounces at lists.maptools.org] On Behalf Of Dave 
>Robertson
>Sent: Sunday, June 25, 2006 7:33 PM
>To: gdal-dev at lists.maptools.org
>Subject: [Gdal-dev] jp2kak on OSX
>
>Frank,
>Thanks for the advice.
>
>./configure --without-python --without-ecw --without-libtool --with- 
>kakadu=< my absolute path to kakadu 5.1 >
>
>Compiling gdal using the above configuration now returns a different  
>set of undefined symbols, but still appears to be using libtool  
>somewhere in the process.
>
>
>ld: Undefined symbols:
>__ZN11kdu_tiffdir12write_headerEP21kdu_compressed_targetx
>__ZN11kdu_tiffdir4initEb
>__ZN11kdu_tiffdir5closeEv
>__ZN11kdu_tiffdir7opendirEP21kdu_compressed_source
>__ZN11kdu_tiffdir8copy_tagERS_j
>__ZN11kdu_tiffdir8open_tagEj
>__ZN11kdu_tiffdir8read_tagEjiPd
>__ZN11kdu_tiffdir8read_tagEjiPj
>__ZN11kdu_tiffdir8read_tagEjiPt
>__ZN11kdu_tiffdir8writedirEP21kdu_compressed_targetx
>__ZN11kdu_tiffdir9write_tagEjiPd
>__ZN11kdu_tiffdir9write_tagEjiPt
>__ZN11kdu_tiffdir10create_tagEj
>__ZN11kdu_tiffdir13get_dirlengthEv
>__ZN11kdu_tiffdir9write_tagEjiPj
>__ZN12jpx_metanode12get_existingERP14jp2_family_src
>__ZN12jpx_metanode14get_descendantEi
>__ZN12jpx_metanode8get_uuidEPh
>__ZN16jpx_meta_manager11access_rootEv
>/usr/bin/libtool: internal link edit command failed
>make[1]: *** [/Volumes/FW28G/FW55G/projects/Searcher/gdal-kdu/ 
>gdal-1.3.2/libgdal.dylib] Error 1
>make: *** [check-lib] Error 2
>
>Any suggestions?
>
>Regards,
>Dave Robertson.
>
>
>>
>> Dave Robertson wrote:
>>> Hi,
>>>
>>> I'm trying to compile GDAL 1.3.2 with Kakadu v5.1 on OSX but make  
>>> fails
>>> with a lot of undefined symbols reported by libtool.
>>> Looking back through the list and gdal changelogs, the latest  
>>> version of
>>> kakadu mentioned is 4.0.2 in GDAL 1.1.9
>>>
>>>>  JP2KAK Driver: Can be used with Kakadu 4.0.2 now.
>>>
>>> Are later versions of kakadu supported, or to do I have to revert
to
>>> Kakadu 4.0.2 ?
>>
>> Dave,
>>
>> I believe I have always used --without-libtool when building 
>in Kakadu
>> support on unix systems.  The problem is that we explicitly pull in
a
>> bunch of object files from Kakadu directly, rather than as a library
>> (because that is the only way Kakadu seems to offer them), and this
>> seriously confuses the libtool build which seems to expect to
control
>> all object files "its way".
>>
>> I'm pretty sure I have tried at least Kakadu 5.0 on Linux, so I
>> don't *forsee* a problem with 5.1 o MacOS X.  Hmm, in fact I'm
pretty
>> sure I tried Kakadu 5.0 or 5.1 on MacOS X a couple weeks ago without
>> any significant problem (using --without-libtool).
>>
>> Best regards,
>> -- 
>
>
>
>
>
>
>
>> Hi,
>>
>> I'm trying to compile GDAL 1.3.2 with Kakadu v5.1 on OSX but make
>> fails with a lot of undefined symbols reported by libtool.
>> Looking back through the list and gdal changelogs, the latest
version
>> of kakadu mentioned is 4.0.2 in GDAL 1.1.9
>>
>>>  JP2KAK Driver: Can be used with Kakadu 4.0.2 now.
>>
>> Are later versions of kakadu supported, or to do I have to revert to
>> Kakadu 4.0.2 ?
>>
>> Thanks,
>> Dave Robertson
>>
>>
>>
>> ld: Undefined symbols:
>> __ZN10jp2_colour4initE16jp2_colour_space
>> __ZN10jp2_source11read_headerEv
>> __ZN10jp2_source14access_paletteEv
>> __ZN10jp2_source15access_channelsEv
>> __ZN10jp2_target12write_headerEv
>> __ZN10jp2_target13access_colourEv
>> __ZN10jp2_target14access_paletteEv
>> __ZN10jp2_target15access_channelsEv
>> __ZN10jp2_target15open_codestreamEb
>> __ZN10jp2_target17access_dimensionsEv
>> __ZN10jp2_target4openEP14jp2_family_tgt
>> __ZN10jp2_targetD1Ev
>> __ZN11jp2_palette12get_num_lutsEv
>> __ZN11jp2_palette15get_num_entriesEv
>> __ZN11jp2_palette4initEii
>> __ZN11jp2_palette7get_lutEiPf
>> __ZN11jp2_palette7set_lutEiPiib
>> __ZN12jp2_channels15get_num_coloursEv
>> __ZN12jp2_channels18get_colour_mappingEiRiS0_S0_
>> __ZN12jp2_channels18set_colour_mappingEiiii
>> __ZN12jp2_channels19get_opacity_mappingEiRiS0_S0_
>> __ZN12jp2_channels19get_premult_mappingEiRiS0_S0_
>> __ZN12jp2_channels19set_opacity_mappingEiiii
>> __ZN12jp2_channels4initEi
>> __ZN12kdu_roi_rectC1E14kdu_codestream8kdu_dims
>> __ZN13jp2_input_boxC2Ev
>> __ZN14jp2_dimensions4initEP10siz_paramsb
>> __ZN14jp2_family_src4openEP21kdu_compressed_source
>> __ZN14jp2_family_src4openEPKcb
>> __ZN14jp2_family_src5closeEv
>> __ZN14jp2_family_tgt4openEPKc
>> __ZN14jp2_family_tgt5closeEv
>> __ZN14jp2_output_box5closeEv
>> __ZTV10jp2_source
>> __ZTV10jp2_target
>> /usr/bin/libtool: internal link edit command failed
>> make[1]: *** [libgdal.la] Error 1
>> make: *** [check-lib] Error 2
>_______________________________________________
>Gdal-dev mailing list
>Gdal-dev at lists.maptools.org
>http://lists.maptools.org/mailman/listinfo/gdal-dev
>