NNTP-Posting-Date: Fri, 15 Aug 2003 13:32:41 -0500 From: Charles Wilkins <2boxers_at_comcast DOT net AT unknown DOT addr> Newsgroups: comp.os.msdos.djgpp,gnu.gcc.help Subject: Re: iostream: No such file or directory with linux to djgpp cross compiler Date: Fri, 15 Aug 2003 14:36:53 -0400 Message-ID: References: X-Newsreader: Forte Agent 1.92/32.570 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 45 NNTP-Posting-Host: 68.45.75.113 X-Trace: sv3-ROl5ChOAicZZSpd+Wya9ib4AepQd/iN3Kl0zzFsNIn85IZttxwM/yUjYVY0tALezvfs8B/uQB+E9UmF!GKOe7J8YHaTg7+8Io+u4wuoGl+7h1lb56mLMvvxD0CkzG0GYiGyU6RvMDoXkMaDjG4oifug= X-Complaints-To: abuse AT comcast DOT net X-DMCA-Complaints-To: dmca AT comcast DOT net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.1 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com >Are you sure you really should have used this --with-headers option? I have built this target a few times now and it has always required this option, but it is possible that something has changed. > >> GNU C++ version 3.3 (i586-pc-msdosdjgpp) >> compiled by GNU C version 3.2 (Mandrake Linux 9.0 3.2-1mdk). > > >Hmmm... that seems to contradict what you wrote further up (quote >moved down by me:) I agree. I set the environment variable CC ahead of time. I am going to redo this build and check the makefiles to see what compiler is actually being used by binutils, gcc, and libstdc++ as they build. >> ignoring nonexistent directory >> "/usr/local/lib/gcc-lib/i586-pc-msdosdjgpp/3.3/../../../../include/c++/3.3" > >This and the following ones appear to be the core of your problem: >*all* the places where it's looking for C++ includes are nonexistent, >it seems, leaving only C-only paths: Yes, but what causes the incorrect paths to be part of the linker search? > >> /usr/local/compiler/cross/djgpp-2.04/lib/gcc-lib/i586-pc-msdosdjgpp/3.3/include >> /usr/local/compiler/cross/djgpp-2.04/i586-pc-msdosdjgpp/sys-include >> /usr/local/compiler/cross/djgpp-2.04/i586-pc-msdosdjgpp/include I did verify that c programs compile and run on the target platform. >> The header in question, , does exist in: >> /usr/local/compiler/cross/djgpp-2.04/include > >That means something's gone seriously wrong. C++ headers should never >be in there. i agree. i was looking at a prior working build for this target and c++ headers were in $prefix/include/c++/3.x Im going to do this all again, isolate why the mandrake compiler was used, and then go from there. Additionally, I am going to build gcc separate from libstdc++ and see if this sheds any light. Thanks, Charles