unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Carl Dong <contact@carldong.me>
Cc: 38061@debbugs.gnu.org
Subject: bug#38061: [minimal reproducer included] libstdc++ mutex references cause clang builds to fail
Date: Tue, 05 Nov 2019 08:59:59 +0100	[thread overview]
Message-ID: <87eeymrbwg.fsf@gmail.com> (raw)
In-Reply-To: <eSiTW2UUtJTf6u776pRq9IOn0Xtf_AMbFsdU--q4iYhE7pmUIrwF33afcWOEbkZOectVMQguqzmyyC-hIu4HRyZS1yS2gAZFePj2SF2tPUA=@carldong.me>


Hello Carl,

> In my original non-minimal build, other things in <mutex> also cause compilation
> errors, which seem odd to me.

This problem is not directly related to <mutex>. You'll have the same
issue with <list>, <vector> or any other header from stdlib.

As explained here:
https://www.mail-archive.com/guix-devel@gnu.org/msg50183.html, the root
cause is that clang cannot find libstdc++ headers which paths are
hardcoded into gcc.

We need to find a clean way to hardcode those paths into clang. However,
I'm not sure on how to proceed cleanly.

Mathieu

      reply	other threads:[~2019-11-05  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 20:29 bug#38061: [minimal reproducer included] libstdc++ mutex references cause clang builds to fail Carl Dong
2019-11-05  7:59 ` Mathieu Othacehe [this message]

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=87eeymrbwg.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=38061@debbugs.gnu.org \
    --cc=contact@carldong.me \
    /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).