latest cvs does not compile on IRIX 6.2

[Greg Dickie]

OK bad etiquette to answer one's own post but casting the mmap64 to (void *)
seems to make my compiler happy.

Greg 

On 15-Dec-98 Greg Dickie wrote:
> 
> Hi,
> 
> CVS tree from this morning:
> Compiling lib/system.c
> "lib/system.c", line 283: error(1119): return value type does not match the
>           function type
>     return mmap64(addr, len, prot, flags, fd, offset);
>            ^
> 
> 1 error detected in the compilation of "lib/system.c".
> *** Error code 2 (bu21)
> 
> 
> here is the man page:
> 
> NAME
>      mmap, mmap64 - map pages of memory
> 
> SYNOPSIS
>      #include <sys/types.h>
>      #include <sys/mman.h>
> 
>      void *mmap(void *addr, size_t len, int prot, int flags, int fd, off_t
>           off);
> 
>      void *mmap64(void *addr, size_t len, int prot, int flags, int fd,
> off64_t
>           off);
> 
> DESCRIPTION
>      The functions mmap and mmap64 establish a mapping between a process's
>      address space and a virtual memory object.  The format of the call is as
>      follows:
> 
>           pa = mmap(addr, len, prot, flags, fd, off);
> 
>      mmap establishes a mapping between the process's address space at an
>      address pa for len bytes to the memory object represented by the file
>      descriptor fd at offset off for len bytes.  The value of pa is an
>      implementation-dependent function of the parameter addr and values of
>      flags, further described below.  A successful mmap call returns pa as
> its
>      result.  The address ranges covered by [pa, pa + len) and [off, off +
>      len) must be legitimate for the possible (not necessarily current)
>      address space of a process and the object in question, respectively.
> 
>      The only difference between mmap and mmap64 is that in mmap64 the off
>      parameter is 64 bits long, so that the file offset can be greater than 2
>      gigabytes.  This is useful for certain filesystem types that support
> such
>      file offsets.
> 
>      The mapping established by mmap replaces any previous mappings for the
>      process's pages in the range [pa, pa + len).
> 
>      The parameter prot determines whether read (load), write (store),
>      execute, or some combination of accesses are permitted to the pages
> being
>      mapped.  The protection options are defined in <sys/mman.h> as:
> 
>           PROT_READ                Page can be read.
>           PROT_WRITE               Page can be written.
>           PROT_EXEC                Page can be executed.
>           PROT_NONE                Page can not be accessed.
> 
> 
> 
> 
> ---------------------------------------------------------------------
> Greg Dickie
> Just A Guy*
> *from discreet logic
> Montreal 
> (514) 954-7171
> greg at discreet.com

---------------------------------------------------------------------
Greg Dickie
Just A Guy*
*from discreet logic
Montreal 
(514) 954-7171
greg at discreet.com