Re: windowscodecs: Workaround libtiff bug when it defines toff_t as 32-bit for 32-bit builds.

[Vincent Povirk]

I have no opinion on this sort of work-around (it should work afaict,
and I haven't found any other places where we currently use toff_t),
but did you file a bug with whatever distro has such broken headers?

windowscodecs: Workaround libtiff bug when it defines toff_t as 32-bit for 32-bit builds.

[Vincent Povirk]

Actually, this will be a problem on libtiff 3.x, where toff_t really
is supposed to be 32-bit.

windowscodecs: Workaround libtiff bug when it defines toff_t as 32-bit for 32-bit builds.

[Austin English]

I had filed a bug with Gentoo:

https://bugs.gentoo.org/show_bug.cgi?id=459820
 On Jul 25, 2013 5:31 PM, "Vincent Povirk" <madewokherd(a)gmail.com> wrote:
> I have no opinion on this sort of work-around (it should work afaict,
> and I haven't found any other places where we currently use toff_t),
> but did you file a bug with whatever distro has such broken headers?

windowscodecs: Workaround libtiff bug when it defines toff_t as 32-bit for 32-bit builds.

[Dmitry Timoshkov]

Vincent Povirk <madewokherd(a)gmail.com> wrote:
> I have no opinion on this sort of work-around (it should work afaict,
> and I haven't found any other places where we currently use toff_t),
> but did you file a bug with whatever distro has such broken headers?

As far as I can see it's not a distro problem, it's a libtiff bug.
> Actually, this will be a problem on libtiff 3.x, where toff_t really
> is supposed to be 32-bit.

Yes, it will be broken for libtiff3, I haven't looked yet how to detect
a libtiff version at compile and run time, if you know how to do that
please let me know.

-- 
Dmitry.