Question about stdlib in gcc-2.95.3-linux toolset
A test of mine is failing in the gcc-2.95.3-linux toolset with the following: ostream: No such file or directory which, I guess, indicates that the std library used by this toolset does not have a <ostream> header. Digging through the regression logs, seems like the library being used is SGI's. Now, there is not defect macro in config/stdlib/sgi.hpp indicating that <ostream> is not available, so my question is: * Is this defect in gcc 2.95 known, and not an installation artifact? * If so, is there any way to figure it out from Boost.Config defect macros or some combination of these and SGI-specific macros? Maybe I'm missing something obvious and this lack of standard headers by gcc 2.95 is common knowledge, I just happen not to have dealt with this compiler ever. Thanks Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
On Tue, Jul 06, 2004 at 02:50:55PM +0200, Joaqu?n M? L?pez Mu?oz wrote:
A test of mine is failing in the gcc-2.95.3-linux toolset with the following:
ostream: No such file or directory
which, I guess, indicates that the std library used by this toolset does not have a <ostream> header. Digging through the regression logs, seems like the library being used is SGI's.
The IOStream parts are not from SGI, IIRC. They are part of libio, written for G++, and are very pre-standard, non-templatised narrow streams.
Now, there is not defect macro in config/stdlib/sgi.hpp indicating that <ostream> is not available, so my question is:
* Is this defect in gcc 2.95 known, and not an installation artifact?
Yes, GCC 2.95 does not provide <ostream>. Both istream and ostream are declared by <iostream>.
* If so, is there any way to figure it out from Boost.Config defect macros or some combination of these and SGI-specific macros?
Errrr, you got me there. I've not seen one. jon -- "Most people with low self-esteem have earned it." - George Carlin
Jonathan Wakely wrote:
On Tue, Jul 06, 2004 at 02:50:55PM +0200, Joaqu?n M? L?pez Mu?oz wrote:
A test of mine is failing in the gcc-2.95.3-linux toolset with the following:
ostream: No such file or directory
which, I guess, indicates that the std library used by this toolset does not have a <ostream> header. Digging through the regression logs, seems like the library being used is SGI's.
The gcc-2.95.3-linux toolset uses gcc 2.95.3 without STLport. <ostream> and other headers are missing from the standard library implementation shipped with gcc 2. The gcc-2.95.3-stlport-4.5.3-linux toolset uses STLPort. There a file named ostream in includes/stlport. There's a switch (_STLP_OWN_IOSTREAMS) that selects between native and STLPort's <ostream>. The STLPort library on the test system is compiled to use STLPort's own stream implementation. HTH, m
participants (3)
-
Joaquín Mª López Muñoz -
Jonathan Wakely -
Martin Wille