Hylafax Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
Re: The Problem on installing HylaFAX at Slackware 3.5 continues
> --Message-Boundary-4205
> Content-type: Application/Octet-stream; name="make.err"; type=Unknown
^^^^^^^^^^^^^^^^^^^^^^^^
Please don't describe plain text attachments as of unknown
binary type; preferably don't attach them at all; embed them
instead. But if you must, code them as the text/plain that they are
and use 7bit transfer encoding, if possible, else quoted printable.
> Content-disposition: attachment; filename="make.err"
> Content-transfer-encoding: BASE64
>
> U2VuZEZheEpvYi5jKys6IEluIG1ldGhvZCBgdW5zaWduZWQgY2hhciBTZW5kRmF4Sm9iOjpj
> cmVhdGVKb2IoY2xhc3MgU2VuZEZheENsaWVudCAmLCBjbGFzcyBmeFN0ciAmKSc6DQpTZW5k
This, when decoded (just the last few lines as the wrong content type
meant that the output didn't go through a pager) still looks like you
need to apply the egcs patch.
Other things to consider with Slackware are that it includes
libz and libtiff, but the libtiff is not compatible with the
default way of building libtiff from source and there are no
utilties. My advice is to use their libtiff and build the
TIFF utilties against the existing library.
Hylafax with the egcs patch definitely does build on Slackware 3.5;
I've done it recently.