From: Apoorv <apoorvs569@gmail.com>
To: 63170@debbugs.gnu.org
Subject: bug#63170: Getting error while trying to compile treesitter plugin for neovim.
Date: Sat, 29 Apr 2023 12:42:18 +0530 [thread overview]
Message-ID: <CAEuo0jgv1eXetxG_H=1bFADE6G-Bm8nk1FZZ910s6TDCU6+a7g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
I'm using the kickstart.nvim configuration,
https://github.com/nvim-lua/kickstart.nvim
And while it tries to compile the treesitter plugin I am getting an error,
```
nvim-treesitter[python]: Error during compilation
In file included from src/scanner.cc:2:
In file included from /home/apoorv/.guix-home/profile/include/c++/vector:66:
In file included from
/home/apoorv/.guix-home/profile/include/c++/bits/refwrap.h:39:
/home/apoorv/.guix-home/profile/include/c++/bits/stl_function.h:439:11:
error: no member named '__is_constant_evaluated' in namespace 'std'
if (std::__is_constant_evaluated())
~~~~~^
/home/apoorv/.guix-home/profile/include/c++/bits/stl_function.h:454:11:
error: no member named '__is_constant_evaluated' in namespace 'std'
if (std::__is_constant_evaluated())
~~~~~^
/home/apoorv/.guix-home/profile/include/c++/bits/stl_function.h:469:11:
error: no member named '__is_constant_evaluated' in namespace 'std'
if (std::__is_constant_evaluated())
~~~~~^
/home/apoorv/.guix-home/profile/include/c++/bits/stl_function.h:484:11:
error: no member named '__is_constant_evaluated' in namespace 'std'
if (std::__is_constant_evaluated())
~~~~~^
4 errors generated.
```
[-- Attachment #2: Type: text/html, Size: 1563 bytes --]
next reply other threads:[~2023-05-01 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 7:12 Apoorv [this message]
2023-08-23 0:49 ` bug#63170: The issue no longer exists Apoorv
2023-09-05 14:46 ` Simon Tournier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEuo0jgv1eXetxG_H=1bFADE6G-Bm8nk1FZZ910s6TDCU6+a7g@mail.gmail.com' \
--to=apoorvs569@gmail.com \
--cc=63170@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).