[Gdal-dev] No python support for x86_64 with kakadu?
Chris Hodgson
chodgson at refractions.net
Mon Nov 1 18:50:48 EST 2004
Alessandro Amici wrote:
>ok. you have the static library. better than nothing :-)
>if you can do without the gdal shared library you may configure
>--without-ld-shared in order to have a clean build and install.
>
>
I think I need the shared library in order to build python. That's the
catch here.
>my ability to help is further hindered by the fact that i have never seen the
>kadaku library ;-), but... it would be nice to see the gcc command line used
>to build the kadaku object files (e.g. args.o). that's the only thing i can
>think off.
>
>
args.o is compiled like this, as are all the files that get copied over
to the gdal src tree:
g++ -I../../coresys/common -I../args -I../image -I../compressed_io
-I../support -O -fPIC
-Wall -Wno-uninitialized -Wno-deprecated -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -c ../args/args.cpp -o args.o
Some other files that are built are compiled like this:
g++ -I../common -O -fPIC -Wall -Wno-uninitialized -c
../coding/block_coding_common.cpp
-o block_coding_common.o
Does that give you any clues? Kakadu doesn't use autoconf, or libtool,
in fact I just get to pick between a bunch of makefiles and edit one of
them to suit. I've already editted it to remove support for MMX (it's
written in assembler which apparently is not 64-bit compatible) and to
add the -fPIC option.
Let me know if you've got any more ideas or if I can give you any more
info to help.
Thanks,
Chris
More information about the Gdal-dev
mailing list