Re: Clang c++ include path

[David Truby <David.Truby@arm.com>]

I've sent a quick fix for this to guix-patches (sorry if I haven't
followed the right process for this!) 
 
I'd like to think more about how to write a make-clang-toolchain
procedure properly so you can pick libstdc++/libc++ versions etc, as my
current implementation is pretty lacking. My patch should fix clang if
all you want is to use the default gcc from guix though.

David Truby

On Mon, 2019-11-11 at 15:12 +0000, David Truby wrote:
> 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.