Re: Clang c++ include path

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 sho

Re: Clang c++ include path

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 >

Re: Clang c++ include path

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 anyt

Re: Clang c++ include path

those Rust >> compilers requires approximately *90 hours* of continuous compiling. > > Are you sure that Rust depends on clang? gnu/packages/rust.scm doesn't have > any > direct reference to "clang" except to remove it. Ah, you're right, Rust depends on LLVM,

Re: Clang c++ include path

> On Nov 7, 2019, at 11:29 AM, Danny Milosavljevic > wrote: > > Are you sure that Rust depends on clang? gnu/packages/rust.scm doesn't have > any > direct reference to "clang" except to remove it. Rust doesn’t depend on clang, it does, however, depend on llvm

Re: Clang c++ include path

> I think that the situation with Rust in that we need to build 18 compilers > is regrettable--I hope that thepowersgang's mrustc can eventually be used > to leapfrog that (it's still active--AND v0.9 has been released) mrustc 0.9 supports bootstrapping Rust 1.29.0. pgpLIAPJtJBi8.pgp Descriptio

Re: Clang c++ include path

Hi Mark, > variable name. The reason is that IceCat depends on Rust which depends > on Clang, and there is a chain of *18* Rust compilers that must be built > before IceCat can be built. On my system, compiling all of those Rust > compilers requires approximately *90 hours* of continuous compili

Re: Clang c++ include path

So here’s my naive suggestion: We should have a MAKE-CLANG-TOOLCHAIN procedure that, given a clang package, a libc package, and a libc++ package (either libc++ or libstdc++), returns a fully-working clang toolchain. I did encounter some problems while attempting this as you can see here: https

Re: Clang c++ include path

Hi, Mark H Weaver skribis: > Ricardo Wurmus writes: > >>> When running clang on a c++ program, it cannot find c++ std libraries. >>> That's because, those libraries path are hardcoded inside g++ compiler >>> and clang cannot find them. >> >> Does this patch help? > > I'd like to request that fi

Re: Clang c++ include path

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 s

Re: Clang c++ include path

Mark H Weaver writes: > Hi Ricardo and Mathieu, > > Ricardo Wurmus writes: > >>> When running clang on a c++ program, it cannot find c++ std libraries. >>> That's because, those libraries path are hardcoded inside g++ compiler >>> and clang cannot find them. >> >> Does this patch help? > > I'd l

Re: Clang c++ include path

Hi Ricardo and Mathieu, Ricardo Wurmus writes: >> When running clang on a c++ program, it cannot find c++ std libraries. >> That's because, those libraries path are hardcoded inside g++ compiler >> and clang cannot find them. > > Does this patch help? I'd like to request that fixes to LLVM/Clan

Re: Clang c++ include path

Hi Mathieu, > When running clang on a c++ program, it cannot find c++ std libraries. > That's because, those libraries path are hardcoded inside g++ compiler > and clang cannot find them. Does this patch help? --8<---cut here---start->8--- diff --git a/gnu/p

Clang c++ include path

Hello, When running clang on a c++ program, it cannot find c++ std libraries. That's because, those libraries path are hardcoded inside g++ compiler and clang cannot find them. This has already been discussed here: https://issues.guix.info/issue/32773, without reaching a solution. Running this

Clang c++ include path

Message-ID: <87r22xxoy6@gmail.com> User-agent: mu4e 1.2.0; emacs 26.3 https://issues.guix.info/issue/32773, mathieu@meru:~/tmp$ ~/.guix-profile/bin/clang t.cpp t.cpp:1:10: fatal error: 'string' file not found mathieu@meru:~/tmp$ ~/.guix-profile/bin/clang -v t.cpp t.cpp:1:10: fatal error: 'st