From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: problems making linux build/host for target msdosdjgpp Date: 7 Nov 2002 16:09:27 GMT Organization: Aachen University of Technology (RWTH) Lines: 40 Message-ID: References: <004201c285fd$3969cb90$021ca8c0 AT helm> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 1036685367 8144 137.226.32.75 (7 Nov 2002 16:09:27 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 7 Nov 2002 16:09:27 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Charles Wilkins 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.