From: Carl Dong <contact@carldong.me>
To: 38061@debbugs.gnu.org
Subject: bug#38061: [minimal reproducer included] libstdc++ mutex references cause clang builds to fail
Date: Mon, 04 Nov 2019 20:29:46 +0000 [thread overview]
Message-ID: <eSiTW2UUtJTf6u776pRq9IOn0Xtf_AMbFsdU--q4iYhE7pmUIrwF33afcWOEbkZOectVMQguqzmyyC-hIu4HRyZS1yS2gAZFePj2SF2tPUA=@carldong.me> (raw)
Hi all,
I'm having another issue with the clang toolchain right now and I've come up
with a minimal reproducer:
Given the following manifest.scm:
--8<---------------cut here---------------start------------->8---
(use-modules (gnu packages gcc)
(gnu packages linux)
(gnu packages llvm))
(packages->manifest
(list clang
(make-libstdc++ gcc)
linux-libre-headers))
--8<---------------cut here---------------end--------------->8---
And test.cpp:
--8<---------------cut here---------------start------------->8---
#include <mutex>
#include <iostream>
typedef std::once_flag once_flag;
int
main()
{
std::cout << "Hello, World\n";
}
--8<---------------cut here---------------end--------------->8---
If you invoke:
--8<---------------cut here---------------start------------->8---
guix environment --manifest=manifest.scm --container --pure -- clang++ test.cpp
--8<---------------cut here---------------end--------------->8---
The output looks like:
--8<---------------cut here---------------start------------->8---
test.cpp:4:14: error: no type named 'once_flag' in namespace 'std'
typedef std::once_flag once_flag;
~~~~~^
1 error generated.
--8<---------------cut here---------------end--------------->8---
In my original non-minimal build, other things in <mutex> also cause compilation
errors, which seem odd to me.
Any help would be very much appreciated!
Cheers,
Carl Dong
contact@carldong.me
"I fight for the users"
next reply other threads:[~2019-11-04 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 20:29 Carl Dong [this message]
2019-11-05 7:59 ` bug#38061: [minimal reproducer included] libstdc++ mutex references cause clang builds to fail Mathieu Othacehe
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='eSiTW2UUtJTf6u776pRq9IOn0Xtf_AMbFsdU--q4iYhE7pmUIrwF33afcWOEbkZOectVMQguqzmyyC-hIu4HRyZS1yS2gAZFePj2SF2tPUA=@carldong.me' \
--to=contact@carldong.me \
--cc=38061@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).