unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Truby <David.Truby@arm.com>
To: "m.othacehe@gmail.com" <m.othacehe@gmail.com>,
	"rekado@elephly.net" <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>, nd <nd@arm.com>
Subject: Re: Clang c++ include path
Date: Mon, 11 Nov 2019 15:12:06 +0000	[thread overview]
Message-ID: <5f44a50d15fd7620bb8fe579a3563f9e220dd28c.camel@arm.com> (raw)
In-Reply-To: <871ruwlpkh.fsf@elephly.net>

Hi,

This patch doesn't work for me as it seems to have a similar issue
finding the libc++ headers.


I do have a fix for the libstdc++ header issue though, I'm just trying
to clean up the patch and then will send it to paches-guix. It involves
patching the source, so will trigger a rebuild of anything depending on
clang (however it doesn't touch llvm). I haven't yet worked out a way
of fixing libc++ but it should be fixable in a similar way.


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?

David Truby
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  parent reply	other threads:[~2019-11-11 15:12 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 [this message]
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

  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=5f44a50d15fd7620bb8fe579a3563f9e220dd28c.camel@arm.com \
    --to=david.truby@arm.com \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@gmail.com \
    --cc=nd@arm.com \
    --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 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).