Date: Mon, 11 Nov 2002 10:28:23 -0500 Message-Id: <200211111528.gABFSNh13357@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f From: DJ Delorie To: djgpp-workers AT delorie DOT com CC: kai DOT ruottu AT luukku DOT com, djgpp-workers AT delorie DOT com, libstdc++@gcc.gnu.org, crossgcc AT sources DOT redhat DOT com In-reply-to: <00af01c28994$cd6293f0$021ca8c0@helm> (message from 2boxers on Mon, 11 Nov 2002 10:12:51 -0500) Subject: Re: cross-gcc build for a linux host for the msdosdjgpp target problems References: <3DCFCF6B DOT 25752 DOT 31A4FAE AT localhost> <00af01c28994$cd6293f0$021ca8c0 AT helm> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > The only thing that hinted me into thinking that there was some significance > to using newlib vs glibc, was the fact that the libstdc++ configure script > was including newlib headers from ~/libstdc++-v3/config/os/newlib instead > djgpp headers from ~/libstdc++-v3/config/os/djgpp That would be a bug.