This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: i686-pc-msdosdjgpp-g++ problems (long)
- From: Stephen M. Webb <stephenw at cryptocard dot com>
- To: Charles Wilkins <chas at pcscs dot com>,djgpp-workers at delorie dot com,libstdc++ at gcc dot gnu dot org
- Date: Fri, 8 Nov 2002 09:00:52 -0500
- Subject: Re: i686-pc-msdosdjgpp-g++ problems (long)
- References: <lrplsuounbjm9n878rvu4e4sobqofcu437@4ax.com>
- Reply-to: stephenw at cryptocard dot com
On November 7, 2002 06:00 pm, Charles Wilkins wrote:
>
> /root/updates/gcc/djgpp/cross/gcc-3.2-obj/i686-pc-msdosdjgpp/libstdc+
>+-v3/include/i686-pc-msdosdjgpp/bits/ctype_base.h:46: `
> _U' was not declared in this scope
> _L' was not declared in this scope
>
> ... many snips of the same error
This error used to come up (ok, many moons ago) when building a
linux-hosted mingw32 cross compiler. I remember patching things
locally to get it to work and the patches were simple but I don't
remember what they were. The problem now no longer occurs with a
mingw32 target out of the box, so I suggest that what you do is check
what is done for mingw32, and try to reproduce that for a djgpp target.
The work lies mostly in the configure scripts and a custom ctype_base
header, if I recall. You may also find you also need to modify the
configury files to fix problems in the cmath headers. Just search for
"mingw" in the config files.
My notes (dated near the end of January) show I had to configure
binutils with the --without-newlib option and install them, install the
target-specific headers in the install tree, then build gcc. I'm not
sure if that's still required.
--
Stephen M. Webb
stephen@bregmasoft.com
stephenw@cryptocard.com