This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: LSB patch to gcc 3.3 tree
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Michael Matz <matz at suse dot de>
- Cc: gdr at acm dot org, dbb at beatties dot us, gcc-patches at gcc dot gnu dot org, mats dot d dot wichmann at intel dot com, anderson at freestandards dot org, dbb at freestandards dot org, libstdc++ at gcc dot gnu dot org
- Date: Wed, 30 Jun 2004 11:24:07 -0500
- Subject: Re: LSB patch to gcc 3.3 tree
- Organization: Red Hat / Chicago
- References: <20040628205604.GF14453@beatties.us><32889.::ffff:128.194.146.36.1088456910.squirrel@webmail.nerim.net><Pine.LNX.4.58.0406290051440.14966@wotan.suse.de><37195.::ffff:24.250.169.187.1088469697.squirrel@webmail.nerim.net><Pine.LNX.4.58.0406290957350.14966@wotan.suse.de><37281.::ffff:24.250.169.187.1088500480.squirrel@webmail.nerim.net><20040629083817.0cafdb3a.bkoz@redhat.com><Pine.LNX.4.58.0406291541130.14966@wotan.suse.de><Pine.LNX.4.58.0406291559420.14966@wotan.suse.de>
>So, question is, is >=3.4 indeed broken, and can I nevertheless use those
>globs for std::__codecvt_abstract_base members?
Superfluous, not really broken.
I've removed this bit, and added the exports that Stewart requested. See gcc-patches.
You should now take the current cvs gcc bits for the ctype/codecvt
exports, and work them into the 3.3. exports. Submit a modified version
of your last patch, taking the previous feedback into account, and
hopefully this will be done!
best,
-benjamin