From: Tomas Volf <~@wolfsden.cz>
To: Baptiste Demoulin <baptiste.demoulin@univ-amu.fr>
Cc: help-guix@gnu.org
Subject: Re: Problem with g++ and iostream
Date: Fri, 1 Mar 2024 11:10:26 +0100 [thread overview]
Message-ID: <ZeGpkh-7-od-zmFx@ws> (raw)
In-Reply-To: <87plweb7b0.fsf@univ-amu.fr>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
On 2024-03-01 10:50:38 +0100, Baptiste Demoulin wrote:
> Hello,
>
> I encountered a problem today with the =g++= compiler from the package
> =gcc-toolchain=. When compiling a simple hello world program:
>
> #+begin_src c++
> #include <iostream>
> int main () {
> std::cout << "Hello World\n";
> return 0;
> }
> #+end_src
>
> with:
> #+begin_src bash
> g++ hello.cc
> #+end_src
>
> I have the following errors, tracing back to the =iostream.h= file:
>
> [..]
>
> Is it a bug, or am I doing something wrong here ?
When I try to compile your source code using
guix shell -C gcc-toolchain -- g++ x.cpp
it does work. Could you try it as well to check whether it will work at least
in a pure environment?
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-01 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 9:50 Problem with g++ and iostream Baptiste Demoulin
2024-03-01 10:10 ` Tomas Volf [this message]
2024-03-01 10:18 ` Baptiste Demoulin
2024-03-01 12:36 ` Baptiste Demoulin
2024-03-01 12:40 ` Baptiste Demoulin
2024-03-01 12:43 ` Baptiste Demoulin
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=ZeGpkh-7-od-zmFx@ws \
--to=~@wolfsden.cz \
--cc=baptiste.demoulin@univ-amu.fr \
--cc=help-guix@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.
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).