all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Clang c++ include path
Date: Tue, 29 Oct 2019 16:37:17 +0100	[thread overview]
Message-ID: <87zhhjbm2u.fsf@gmail.com> (raw)
In-Reply-To: <871ruwlpkh.fsf@elephly.net>


Hello Ricardo,

> Does this patch help?
>
> --8<---------------cut here---------------start------------->8---
> diff --git a/gnu/packages/llvm.scm b/gnu/packages/llvm.scm
> index 9efb4a4841..3c59e8d26d 100644
> --- a/gnu/packages/llvm.scm
> +++ b/gnu/packages/llvm.scm

Thanks for your patch. It seems that it forces clang to use llvm libc++
library. Is this really what we want? Wouldn't we prefer to force clang
to use GNU's libstdc++?

For comparison sake, nix has a default clang that uses GNU's libstdc++
and as a "clang-cxx" that uses libcxx.

I think it is important to fix this issue because all external tools
(such as lsp servers) that rely on clang are currently broken in Guix.

Thanks,

Mathieu

  parent reply	other threads:[~2019-10-29 15:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28  8:30 Clang c++ include path Mathieu Othacehe
2019-10-28 17:58 ` Ricardo Wurmus
2019-10-28 22:08   ` Mark H Weaver
2019-10-28 22:48     ` Marius Bakke
2019-11-03 14:30     ` Ludovic Courtès
2019-11-07 16:29     ` Danny Milosavljevic
2019-11-07 17:34       ` Danny Milosavljevic
2019-11-07 18:43       ` Carl Dong
2019-11-07 19:52       ` Mark H Weaver
2019-10-29 15:37   ` Mathieu Othacehe [this message]
2019-11-11 15:12   ` David Truby
2019-11-11 17:17     ` Mathieu Othacehe
2019-11-13 16:59     ` David Truby
  -- strict thread matches above, loose matches on Subject: below --
2019-11-07  3:17 Protonmail Bridge
2019-10-28  8:19 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhhjbm2u.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.