public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: HHN <harihara.sn@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Errors when trying to use C++ modules with cmake and GCC
Date: Wed, 8 Feb 2023 12:27:42 +0000	[thread overview]
Message-ID: <CAH6eHdTihhcD=NEw5j_RY5cuVNWEV8d5uS88o3pcn9hK7KNUow@mail.gmail.com> (raw)
In-Reply-To: <CAG6c7rUD0QiMcaOAxoN0wYycLKw8p5D4pAhxMJSutN0zw4Woww@mail.gmail.com>

On Wed, 8 Feb 2023 at 12:14, HHN wrote:
>
> I apologise for not providing the complete context, after compiling I had tried to build the test suite and faced errors. I have attached the logs of this failure. ninja fails with
> ninja: build stopped: subcommand failed.
>
> No such issues had occurred with g++-11. Only changes made to was changing the compiler in CMake

error: ‘intmax_t’ is not a member of ‘std’; did you mean ‘intmax_t’?

This is clearly a bug in the software. If you want to use
std::intmax_t you need to include <cstdint> not <stdint.h>. If you
want to include <stdint.h> then you need to use ::intmax_t not
std::intmax_t.

The C++ library headers are cleaner than in previous releases and so
buggy code that used to compile is now rejected.
https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes

  reply	other threads:[~2023-02-08 12:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 10:52 HHN
2023-02-01 11:00 ` Jonathan Wakely
2023-02-08  9:48   ` HHN
2023-02-08 10:35     ` Jonathan Wakely
2023-02-08 12:14       ` HHN
2023-02-08 12:27         ` Jonathan Wakely [this message]
2023-02-08 12:32           ` Jonathan Wakely

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='CAH6eHdTihhcD=NEw5j_RY5cuVNWEV8d5uS88o3pcn9hK7KNUow@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=harihara.sn@gmail.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).