Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: libtiff 3.5 (Incoming faxes trashed)
- To: flexfax@sgi.com
- Subject: Re: flexfax: libtiff 3.5 (Incoming faxes trashed)
- From: Dmitry Bely <dbely@mail.ru>
- Date: 01 May 2000 23:17:44 +0400
Hal Snyder <hal@vailsys.com> writes:
> > Don't ever try [libtiff] 3.5 -- it will not work!
>
> I assume this applies for *all* platforms, not just Red Hat Linux
> which was the context of the previous remark.
Yes. Due to the serious design flaw Hylafax depends on some internal
libtiff data structures, which were changed in version 3.5.
> Is this documented somewhere on the Hylafax website? I did a quick
> scan and didn't find it.
AFAIK no, but it was discussed in Hylafax developer's mailing list about a
month ago.
> Libtiff-3.4 is going to get harder and harder to find as time goes by.
> Does anyone have an idea how much work is involved in porting to the
> new lib? Or should forthcoming releases of hylafax include source for
> libtiff-3.4 (yuck)?
Possibly 4.1 beta 3 will be libtiff 3.5 compatible. Robert Colquhoun has
already made the patch. Unfortunately, Hylafax <-> libtiff interface has
not been fixed, so the similar problems very likely to happen in future.
Hope to hear from you soon,
Dmitry