From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "jm@samuelinteriors.com" <jm@samuelinteriors.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: gcc update help please
Date: Wed, 22 Jun 2022 21:04:51 +0100 [thread overview]
Message-ID: <CAH6eHdT4zxuUpFher2Gomdii9voGPk7pS3kq7Mdqb0xjoSb_sw@mail.gmail.com> (raw)
In-Reply-To: <62B36A9D.20601@samuelinteriors.com>
On Wed, 22 Jun 2022 at 20:19, jm@samuelinteriors.com
<jm@samuelinteriors.com> wrote:
>
> Hello.
>
> I have installed the stand alone CodeBlocks 17.12 .
>
> It came with mingw32-gcc-5.1.0.exe .
That's ancient.
>
> I am having some difficulty compiling commands like std::codecvt_utf8
> and others.
GCC 5.1 does have the std::codecvt_utf8, so I assume you're not using
the -std=c++11 option.
> I have looked at the page
> https://en.cppreference.com/w/cpp/locale/codecvt_utf8 and they have a
> list of compilers that work with their code.
>
> I tried some of the gcc versions and found that GCC 5.2 (C++11) works OK
> with it.
No it doesn't, the std::codecvt_utf8 in GCC 5.2 is identical to the
one in GCC 5.1 and it doesn't handle UCS2 correctly (see
https://gcc.gnu.org/PR79980 for details).
The oldest versions to compile that code correctly are GCC 5.5 or
anything >= 6.4
> Therefore, my question for you is:
>
> Where do I get a GCC 5.2 (C++11) download from you guys?
You don't, sorry. The GCC project does not provide precompiled binaries.
https://gcc.gnu.org/install/binaries.html
I suggest you try to get a newer version of the mingw port of GCC,
which you can get from the mingw project. You might want to try
something other than CodeBlocks.
>
> Or maybe if GCC 5.5 would work for my computer. Maybe?
It should do.
next prev parent reply other threads:[~2022-06-22 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 19:16 jm
2022-06-22 20:04 ` Jonathan Wakely [this message]
2022-06-24 7:53 sotrdg sotrdg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH6eHdT4zxuUpFher2Gomdii9voGPk7pS3kq7Mdqb0xjoSb_sw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jm@samuelinteriors.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).