Le jeudi 16 septembre 2010 22:54:16, James Meyer a écrit :
> Oh okay. Thanks!
>
> All the while I thought I was doing something wrong.
> I'm assuming the fix won't be reflected in the version that is available
> from the Ubuntu repositories, right?
It's up to the Ubuntu packagers. You'll probably
Oh okay. Thanks!
All the while I thought I was doing something wrong.
I'm assuming the fix won't be reflected in the version that is available
from the Ubuntu repositories, right?
In other words I will need to build GDAL from source then?
Regards
James
On 16/09/2010 21:29, Even Rouault wrote
James,
ok, I confirm the bug. This was indeed specific to the new implementation of
the
PCIDSK driver that came in 1.7.0.
See http://trac.osgeo.org/gdal/ticket/3755 for the fix
Le jeudi 16 septembre 2010 20:57:51, James Meyer a écrit :
> Hi Even
>
> Thanks for the reply. I ran your code and
Hi Even
Thanks for the reply. I ran your code and it doesn't block with your
sample tiff file.
It blocks with any .pix files (driver: PCIDSK Database File) with the
output being:
*
in thread
finished
/
/I am running Ubuntu 10.04 and have GDAL 1.7 on my
James,
what you see is a bit surprising...
Do you build GDAL by yourself or use a packaged version ? If you build it
yourself, you explicitely need to specify --with-threads at ./configure time
(unless you use the latest trunk version where it is now the default). In
port/cpl_multiproc.h, you
Hi
I am opening a GDALDataset in my main thread which I then pass to a
second thread for processing. Only the second thread accesses the dataset.
As soon as the thread makes a call to GDALRasterBand::RasterIO() the
thread blocks indefinitely.
Could you please explain to me why this is happe
