Update: I think I've reproduced the problem at earlier commits as well, so I don't think it's really the commit I cited. I now believe that the machine that was exhibiting the problem had multiple installs of both libtiff and other libraries. After ensuring that this is no longer the case, the symptoms appear to have evaporated, so... nothing to see here, folks. Sorry to bother you.
> On Sep 23, 2025, at 4:19 PM, Olivier Paquet <[email protected]> wrote: > > Le mar. 23 sept. 2025, à 17 h 57, Larry Gritz <[email protected] > <mailto:[email protected]>> a écrit : >> Um, maybe libjpeg vs libjpeg-turbo could be responsible here? >> >> I have old-style JPEG enabled when building libtiff. But I think this >> failing configuration is one where I'm using jpeg-turbo instead of libjpeg. >> They're supposed to be compatible, but maybe there is a subtle difference in >> behavior here? > > I rebuilt with jpeg support and did not get the error you did. I'm using > libjpeg-turbo 3.1.1. But I now notice that you're going through the wrong > code path entirely. The message you get is not for old-style jpeg but rather > in the new jpeg reading code. I have no idea how you're getting there with > that file. > > Olivier -- Larry Gritz [email protected]
_______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
