Re: flexfax: hylafax beta and Linux 2.2.x

[Robert Colquhoun <rjc@trump.net.au>]

Hi,

At 12:11 AM 5/16/99 -0400, Dave Wreski wrote:
>> Could you look up the prototypes of these functions, either from
>> /usr/lib/stdlib.h or the man pages.  It looks like somehow hylafax has
>> decided to generate its own mktemp() and mkstemp() functions which are
>> conflicting with the standard ones provided by linux.
>
>/usr/include/stdlib.h:extern char *mktemp __P ((char *__template));
>/usr/include/stdlib.h:extern int mkstemp __P ((char *__template));
>
>I guess they're external because they're defined in the library?
>
>>>/usr/include/unistd.h:791: warning: declaration of `getpass(const char *)' 
>>>throws different exceptions
>> 
>> Same as above i think, could you cut and paste the linux prototype.
>
>/usr/include/unistd.h:extern char *getpass __P ((__const char *__prompt));
>

Try this patch to configure(i don't think it is looking in the right
include files):
$ diff configure.orig configure
2351c2351
<     CheckFuncDecl mkstemp 'extern int mkstemp(char *);' stdio.h unistd.h
---
>     CheckFuncDecl mkstemp 'extern int mkstemp(char *);' stdlib.h stdio.h
unist
d.h
2359c2359
<     CheckFuncDecl getpass 'extern char* getpass(const char *);' stdlib.h
---
>     CheckFuncDecl getpass 'extern char* getpass(const char *);' stdlib.h
unist
d.h
2437c2437
<     CheckFuncDecl mktemp 'extern char* mktemp(char*);' stdio.h unistd.h
---
>     CheckFuncDecl mktemp 'extern char* mktemp(char*);' stdlib.h stdio.h
unistd.h          



>Hmm.. Hope that's not too difficult..

Not sure - there are easy fixes(like as Aiden mentioned define the
__USE_XOPEN or change all refs in Dispatcher.c++ from fds_bits to
__fds_bits) but this is not something you would generally want to add to
the source code.

You might want to try the above just to get it to compile, to make sure the
rest of the build process succeeds.

>
>> Depends on your firewall....should not normally be a problem if you are
>> only running a cvs client(ie downloading the hylafax source code).  A cvs
>> server is another matter and probaly would require firewall configuration.
>
>Yes, I meant from a client perspective.. Without trying to figure out the hard
>way, which ports does it use, for example?

For pserver cvs normally 2401(this is what cvs.hylafax.org uses for anon
access), also can work by rsh or ssh.

>
>> I am not sure if anyone has yet has tried RH 6.0, it is not available in
>> Australia until next week.
>
>I'll send you a CDROM if you need it...
>

Thanks - i really appreciate the offer, but i will wait for the Aust
version, it shouldn't be far away.  One reason why its delayed i think is
that we have to wait for the international version.  I believe the US
version contains some too strong encryption logic and can't be
exported(...or something).

- Robert