[Gdal-dev] ECW File open failed

[Ken Sewell]

I'm running off of the GDAL CVS (16 Jan) with the ecwsdk-3.2.11Jun2005 
package.  Gdal showed ecw support in the configure step. Both built and 
installed.  When I run gdalinfo on an ecw file I get the following:

ERROR 1: File open failed - 1
GDALOpen failed - 1
File open failed


This seems to be the relavent part of the strace dump:

open("Nellis_AFB_1m.aux", O_RDONLY)     = -1 ENOENT (No such file or directory)
open("Nellis_AFB_1m.aux", O_RDONLY)     = -1 ENOENT (No such file or directory)
open("Nellis_AFB_1m.ecw", O_RDONLY)     = 4
read(4, "e\2\1\2\10\4\0\0YV\0\0L\10\0\3\0\1\0@\0@\0\31\1\0\0\0\0"..., 8192) = 8192
close(4)                                = 0
mmap(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|0x40, -1, 0) = 0x40000000
mprotect(0x40000000, 4096, PROT_NONE)   = 0
clone(child_stack=0x40800270, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tidptr=0x408009f0, tls=0x40800960, child_tidptr=0x408009f0) = 22081
futex(0x50edb8, FUTEX_WAKE, 1)          = 1
open("", O_RDONLY)                      = -1 ENOENT (No such file or directory)
open("", O_RDONLY)                      = -1 ENOENT (No such file or directory)
close(4294967295)                       = -1 EBADF (Bad file descriptor)
close(4294967295)                       = -1 EBADF (Bad file descriptor)
write(2, "ERROR 1: File open failed\n", 26) = 26
close(3)                                = 0
munmap(0x2aaaab06c000, 4096)            = 0
write(2, "GDALOpen failed - 1\nFile open failed", 37) = 37
sched_getparam(22081, { 0 })            = 0
sched_getscheduler(22081)               = 0 (SCHED_OTHER)
sched_yield()                           = 0
nanosleep({0, 1000}, NULL)              = 0


I'm running on SuSE 10.0/64-bit.  Can anyone shed some light on this for me?  Thanks.

Ken