|
From: | GNU bug Tracking System |
Subject: | bug#63170: closed (Getting error while trying to compile treesitter plugin for neovim.) |
Date: | Tue, 05 Sep 2023 16:07:06 +0000 |
Your message dated Tue, 05 Sep 2023 16:46:05 +0200 with message-id <86h6o8u18y.fsf@gmail.com> and subject line Re: bug#63170: The issue no longer exists. has caused the debbugs.gnu.org bug report #63170, regarding Getting error while trying to compile treesitter plugin for neovim. to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 63170: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63170 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: Getting error while trying to compile treesitter plugin for neovim. Date: Sat, 29 Apr 2023 12:42:18 +0530 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.
```
--- End Message ---
--- Begin Message ---Subject: Re: bug#63170: The issue no longer exists. Date: Tue, 05 Sep 2023 16:46:05 +0200 Hi, On Wed, 23 Aug 2023 at 06:19, Apoorv <apoorvs569@gmail.com> wrote: > The issue seems to be fixed now. It's been a while actually, I just forgot > to respond here. Thanks for the notification. So I am closing. Cheers, simon
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |