3ksnn64@cadlab.ecn.purdue.edu (Joe Cychosz) (11/07/90)
Hi, Has anyone had any luck porting C++ 2.0 to the latest IRIX release (3.3.1)? I seem to have some kind of problem with the include files in /usr/include/CC. For example: in math.h, complaints about fmod, in stdio.h, complaints about _filbuf and _flsbuf, I have noticed that _semgetc and _semputc do not get defined and have to be added by hand. This happened at 3.2 also. libc.h is quite a mess as well. I think the solution might be to just copy relevent #defines and the like and delete the #include <cc/*.h>. Joe
bean@putter.wpd.sgi.com (David (Bean) Anderson) (11/13/90)
In article <1990Nov7.034736.14795@ecn.purdue.edu>, 3ksnn64@cadlab.ecn.purdue.edu (Joe Cychosz) writes: |> |> Hi, |> |> Has anyone had any luck porting C++ 2.0 to the latest IRIX release (3.3.1)? |> |> I seem to have some kind of problem with the include files in |> /usr/include/CC. For example: |> |> in math.h, complaints about fmod, |> in stdio.h, complaints about _filbuf and _flsbuf, I have noticed that |> _semgetc and _semputc do not get defined and have to be added by hand. |> This happened at 3.2 also. |> libc.h is quite a mess as well. |> |> I think the solution might be to just copy relevent #defines and the |> like and delete the #include <cc/*.h>. |> |> Joe SGI has recently released it's 2.0 based C++ product. There are dozens of bug fixes in it as well as major changes in header files. The list price is $1195 and may be quite a bit cheaper with a university discount. Bean
doelz@urz.unibas.ch (11/14/90)
In article <1990Nov13.010036.20278@relay.wpd.sgi.com>, bean@putter.wpd.sgi.com (David (Bean) Anderson) writes: > > SGI has recently released it's 2.0 based C++ product. There are > dozens of bug fixes in it as well as major changes in header files. > The list price is $1195 and may be quite a bit cheaper with > a university discount. > We have a license for it but no upgrade. What does 'recently' mean? We're still on the 'old' release - no documentation, reference or user guide in any printed form. All we have is Documet Number 007-3356-010, (the 'release notes'), the man page and a maintenance contract covering the software product which has been of no comprehensive impact so far. Reinhard