RE: [pooma-dev] notes on compiling for gcc-2.96-RH (and small bug ?)

[James Crotinger]

We have, at times, tried to institute a policy of not including <iostream> in any of the public headers. Perhaps this was abandoned at some point. There are a number of places where <ios> and <iosfwd> should suffice, though. (I haven't looked at these specific examples.)

Since gcc 3.1 is out, it would be best to keep the LINUXgcc configuration appropriate for it, and perhaps add a LINUXgcc296 or something for changes necessary to keep it compiling with the older compiler.

        Jim

> -----Original Message-----
> From: Garnet Kin-Lic Chan [mailto:address@hidden]
> Sent: Wednesday, July 17, 2002 1:00 AM
> To: address@hidden
> Subject: [pooma-dev] notes on compiling for gcc-2.96-RH (and
> small bug?)
>
>
>
>
> I've found that I need to make a few changes to compile
> for this version of gcc, one of
> which is due to a small bug I believe.
>
> choose arch LINUXgcc
> in /lib/$ARCH/PoomaConfiguration.h,
> #define POOMA_MISSING_IO_MANIPS POOMA_YES
> #define POOMA_NO_STD_IOSBASE POOMA_YES
>
> in src/$ARCH/IO/DiskLayout.cmp.cpp, change #include <ios> to
> #include <iostream>
>
> in src/$ARCH/IO/DiskLayout.h there is no #include <string> (I
> believe this is an error). Add this to the header.
>
> in src/Tiny/Vector.h, change #include <ios> to #include <iostream>.
>
> Garnet
>
>
>