unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: David Truby <David.Truby@arm.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, nd <nd@arm.com>
Subject: Re: Clang c++ include path
Date: Mon, 11 Nov 2019 18:17:03 +0100	[thread overview]
Message-ID: <87a792bahi.fsf@gmail.com> (raw)
In-Reply-To: <5f44a50d15fd7620bb8fe579a3563f9e220dd28c.camel@arm.com>


Hello David,

> I actually have two ways of fixing it though and am unsure which is
> more appropriate. The non-controversial one is to just get the
> libstdc++ header directory for the default gcc and patch clang to look
> there. However, as an end user of the clang package I would rather have
> a make-clang-toolchain procedure that takes a gcc-toolchain version and
> gets the standard library from that. I've got implementations of both
> of these, does anyone have an opinion which one would be preferred?

At first glace, the second option seems better but don't hesitate to
post both versions and we'll discuss them :)

Thanks,

Mathieu

  reply	other threads:[~2019-11-11 17:17 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
2019-11-11 15:12   ` David Truby
2019-11-11 17:17     ` Mathieu Othacehe [this message]
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

  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=87a792bahi.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=David.Truby@arm.com \
    --cc=guix-devel@gnu.org \
    --cc=nd@arm.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. 
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).