Re: flexfax: Redhat 5.0: compilation problems

[Phil Watkinson <pkw@elgro.co.uk>]

At 22:59 09/02/1998 +0100, Michael Agbaglo wrote:
>Did someone managed to compile and install hylafax4.0pl1 successfully ?
>Installtion fails on my machine due to lib-function incompatibility.
>
>:-/
>

Me too :(

I see this warning on the compilation of faxmsg, and then fairly frequently
thereafter :

/usr/lib/libutil.so: warning: revoke is not implemented and will always fail

Also there is a number of warnings about 4 functions in Socket.h :

Socket.h: In function `static int Socket::accept(int, void *, int *)':
In file included from InetTransport.c++:41:
Socket.h:65: warning: passing `int *' as argument 3 of 
            `accept(int, sockaddr *, unsigned int *)' changes signedness
Socket.h: In function `static int Socket::getpeername(int, void *, int *)':
Socket.h:71: warning: passing `int *' as argument 3 of 
            `getpeername(int, sockaddr *, unsigned int *)' changes signedness
Socket.h: In function `static int Socket::getsockname(int, void *, int *)':
Socket.h:73: warning: passing `int *' as argument 3 of 
            `getsockname(int, sockaddr *, unsigned int *)' changes signedness
Socket.h: In function 
         `static int Socket::setsockopt(int, int, int, const void *, int)':
Socket.h:75: warning: passing `const char *' as argument 4 of 
         `setsockopt(int, int, int, void *, unsigned int)' discards const

My Readhat 5.0 has been upgraded with those packages recommended in the
'errata', and perhaps this is the problem - I should have time tonight to
try to find where my '/usr/lib/libutil.so' came from.

Could a C++ expert tell us if the Socket.h warnings are important ?

Later,
Phil Watkinson,
Boston, UK.