From octave-maintainers-request at bevo dot che dot wisc dot edu Wed Feb 19 17:47:27 2003
Subject: Re: Failure building CVS on IRIX 6.5 with GCC
From: Paul Kienzle <pkienzle at users dot sourceforge dot net>
To: octave-maintainers at bevo dot che dot wisc dot edu
Date: Wed, 19 Feb 2003 18:47:33 -0500

Albert Chin wrote:

>On Wed, Feb 19, 2003 at 03:42:56PM -0600, John W. Eaton wrote:
>  
>
>>On 19-Feb-2003, Albert Chin <octave-maintainers at thewrittenword dot com> wrote:
>>
>>| While building CVS on IRIX 6.5.19 with GCC 3.2.2. Any ideas?
>>
>>| g++ -c -I/opt/TWWfsw/readline42a/include -L/opt/TWWfsw/ncurses5/include -I/opt/TWWfsw/libfftw21/include -I. -I.. -I../liboctave -I../src -I../libcruft/misc  -I../glob -I../glob -DHAVE_CONFIG_H  -O2 syscalls.cc -o syscalls.o
>>| syscalls.cc: In function `Octave_map mk_stat_map(const file_stat&)':
>>| syscalls.cc:69: conversion from `ino_t' to `const octave_value' is ambiguous
>>
Octave is looking for ino_t

>>
>>What is the actual type of ino_t on your system?
>>    
>>
>
>typedef unsigned __uint32_t;
>typedef __uint32_t o_ino_t;
>
You have reported o_ino_t

If you look a few lines down in the header, you will
see that ino_t is 64 bit.  I put a static_cast<double>
around it for my IRIX build.  Is there a system independent
way of representing 64 bit values?

Paul Kienzle
pkienzle at users dot sf dot net