![]() |
Do you maintain the distribution? Seem that someone should include the newest patches in it, detecting whether to use them in ./configure or somethin'. I'd be willing to help, working under your direction. Ken Berland The Heroic Sandwich 630 Idaho Ave., #303 Santa Monica CA 90403 (310) 393 7981 Phone (310) 383 7981 Cell On Mon, 15 Mar 1999, David Woolley wrote: > > 5000 bytes of which < 1000 contain the message and this doesn't count > headers, but does include a digital signature that is three times the > size of the message - at least PGP doesn't include the full certificate > chain! > > > > Has anyone successfully compiled Hylafax v4.0pxx unde Linux? I keep > > Many. From all accounts most installations are under Linux, many using > the Red Hat binaries, although I have reservations about the support for > these and the number of versions. (NB most development is not on Linux.) > An initial scan of the list would have told you this. > > When referencing Linux, please quote the distribution, otherwise we > have to assume the current Red Hat (a problem with Red Hat users). > > > SendFaxJob.c++:496: no matching function for call to > > `SendFaxClient::sendZData > > I assume that you have more than one of these errors, in which case get > and apply the egcs patch (also know as the gcc (can't remember version) > patch). I think this was the only critical patch to allow compilation > on Slackware 3.5. > > This is a 1 to 2 a week FAQ. > > > and also loads of error messages for libfaxutil.a, such as: > > If the compilations fail, not library is created. The hylafax Makefile > is strange in that it does not give up after the first error. > > > I have tried compiling different iterations of the v4.0pxx software (and > > does > > 4.0pl2 with relevant patches is the only applicable version these days. >