From: Fredrik Salomonsson <plattfot@posteo.net>
To: Laurent Gatto <laurent.gatto@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: C++ error
Date: Wed, 13 Nov 2024 00:50:34 +0000 [thread overview]
Message-ID: <877c982bz9.fsf@posteo.net> (raw)
In-Reply-To: <CA+uNOzjbPM5Km4ryj74P_hWsY4rt=zKUJN54XRLs7avL_jj7KQ@mail.gmail.com>
Hi,
Laurent Gatto <laurent.gatto@gmail.com> writes:
> Hi Fredrik,
>
> Thank you for taking the time looking into this.
No worries.
>
> My issue doesn't seem to be related to an old gcc version.
>
> ```
> $ g++ --version
> g++ (GCC) 14.2.0
> Copyright (C) 2024 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> ```
>
> My location is different though
>
> ```
> $ which g++
> /home/lgatto/.guix-profile/bin/g++
> ```
> Checking the stdc++ lib:
>
> ```
> $ sed -n '3154p' ~/.guix-profile/include/c++/type_traits
> _GLIBCXX20_DEPRECATED("use is_standard_layout_v && is_trivial_v instead")
> ```
>
> And the gcc search paths on my machine:
>
> ```
> $ echo | g++ -E -Wp,-v -
> ignoring nonexistent directory "/no-gcc-local-prefix/include"
> ignoring nonexistent directory
> "/gnu/store/ikn0imxfc6n0ba12mrf0c4hc1jm7ylc7-gcc-14.2.0-lib/lib/gcc/x86_64-unknown-linux-gnu/14.2.0/../../../../../../../x86_64-unknown-linux-gnu/include"
> ignoring duplicate directory "/home/lgatto/.guix-profile/include"
> as it is a non-system directory that duplicates a system directory
> #include "..." search starts here:
> #include <...> search starts here:
> /home/lgatto/.guix-profile/include
> /gnu/store/ikn0imxfc6n0ba12mrf0c4hc1jm7ylc7-gcc-14.2.0-lib/lib/gcc/x86_64-unknown-linux-gnu/14.2.0/include
> /gnu/store/ikn0imxfc6n0ba12mrf0c4hc1jm7ylc7-gcc-14.2.0-lib/lib/gcc/x86_64-unknown-linux-gnu/14.2.0/include-fixed
> /gnu/store/zvlp3n8iwa1svxmwv4q22pv1pb1c9pjq-glibc-2.39/include
> End of search list.
> # 0 "<stdin>"
> # 0 "<built-in>"
> # 0 "<command-line>"
> # 1 "/home/lgatto/.guix-profile/include/stdc-predef.h" 1 3
> # 0 "<command-line>" 2
> # 1 "<stdin>"
> ````
>
> Except for the version and location, all this looks very similar to
> what you have, which leaves me quite puzzled.
Indeed, this is strange.
What does `guix package -I gcc` and `guix package -I stdc\+\+` give you?
Maybe it'll show you some discrepancies.
And if this is any help this is the commit I'm using for guix:
```
$ guix describe
Generation 142 nov 09 2024 12:47:04 (current)
…
guix 14abf6e
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 14abf6e19e5c24fa690a443f5467e7f0b6eafcc5
```
Note: I removed the other channels I'm using and replaced them with `…`.
None of them defines any gcc related packages so they should not affect
this.
--
s/Fred[re]+i[ck]+/Fredrik/g
next prev parent reply other threads:[~2024-11-13 1:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 7:41 C++ error Laurent Gatto
2024-11-12 17:54 ` Fredrik Salomonsson
2024-11-12 20:26 ` Laurent Gatto
2024-11-13 0:50 ` Fredrik Salomonsson [this message]
2024-11-13 6:49 ` Laurent Gatto
2024-11-13 19:12 ` Fredrik Salomonsson
2024-11-13 21:33 ` Laurent Gatto
2024-11-14 18:51 ` Fredrik Salomonsson
2024-11-16 10:56 ` Laurent Gatto
2024-11-16 13:19 ` Laurent Gatto
2024-11-18 18:49 ` Fredrik Salomonsson
2024-11-21 8:50 ` Laurent Gatto
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=877c982bz9.fsf@posteo.net \
--to=plattfot@posteo.net \
--cc=help-guix@gnu.org \
--cc=laurent.gatto@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).