Mail Archives: djgpp/2002/11/07/11:16:24
Charles Wilkins <chas AT pcscs DOT com> wrote:
> as every C++ programmer knows, the C++ standard library does in fact
> include C with few exceptions.
You're partly mixing up the library implementation with library usage.
Yes, C++ does let you use C standard library functions. But no, that
does not mean a C++ compiler maker, or even a C++ runtime maker, must
supply its own copy of an implementation of the C libraries. You just
have to make sure that some implementation exists, and is found by the
compiler / linker.
> Isn't the ANSI / ISO C++ Standard Libray ( libstdc++ ) along with its
> headers (non-deprecated or 'C++ified' headers and STL headers)
> supposed to build with the linux hosts crossgcc.
Yes, it is. *If* it's built at all, that is. All that really matters
in the end is that you have a set of headers and library files. It
doesn't matter where it came from.
> I just want to be clear that I will be able to build a cross gcc that
> makes DOS executables with the same full C++ support that a natively
> built GCC-3.2 can do.
It should be possible, indeed. But getting it done may require more
insight into the GCC build process' intricacies than either you or I
have, off the top of our heads. Andris should be able to provide more
insight, but he doesn't seem to be listening right now.
>>You might just cheat and install the libraries of the native DJGPP GCC
>>build, of course.
> I tried linking against them and it didn't work.
Linking alone won't be enough. You'll have to use the natively built
headers, too, than. And put them in a place that makes absolutely
sure they're found, instead of the host system's ones.
--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.
- Raw text -