This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: mingw32 target broken [cygwin as well] [the saga continues]
Craig Rodrigues <rodrigc@mediaone.net> writes:
> > _U' was not declared in this scope
> > /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:47: `
> > _L' was not declared in this scope
> > /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:48: `
> > _U' was not declared in this scope
> > /home/megacz/gcc-3.1/bin/i686-pc-mingw32/libstdc++-v3/include/i686-pc-mingw32/bits/ctype_base.h:48: `
> > _L' was not declared in this scope
>
> and this patch from bkoz:
> http://gcc.gnu.org/ml/libstdc++/2001-03/msg00144.html
A bit stale, but I was able to hand-edit for the same effect, and it
worked.
I'm not too familiar with the administrative end of the gcc project --
is there some patch-approval process that patches like this have not
gone through? Is that why they don't end up getting back into the
trunk? Otherwise, may I post a diff to the latest CVS in the hopes of
getting it folded in?
I've also noticed that the configure in the root directory of the gcc
checkout does not pass the --target=$TARGET option to the invocation
of configure for libstdc++-v3, although it does pass --with-target-dir
-- can anybody verify this and/or advise me on how to fix it "the
right way"? (right now I'm just manually re-running configure for
libstdc++-v3).
- a