[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Failure building CVS on IRIX 6.5 with GCC
From: |
Albert Chin |
Subject: |
Re: Failure building CVS on IRIX 6.5 with GCC |
Date: |
Thu, 20 Feb 2003 07:57:11 -0600 |
User-agent: |
Mutt/1.4i |
On Wed, Feb 19, 2003 at 06:47:33PM -0500, Paul Kienzle wrote:
> Albert Chin wrote:
>
> >On Wed, Feb 19, 2003 at 03:42:56PM -0600, John W. Eaton wrote:
> >
> >
> >>On 19-Feb-2003, Albert Chin <address@hidden> 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?
You're right:
typedef unsigned long long __uint64_t;
typedef __uint64_t ino_t;
--
albert chin (address@hidden)