From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Clang c++ include path
Date: Thu, 07 Nov 2019 14:52:50 -0500 [thread overview]
Message-ID: <87lfsrihua.fsf@netris.org> (raw)
In-Reply-To: <20191107172931.54508e52@scratchpost.org>
Hi Danny,
Danny Milosavljevic <dannym@scratchpost.org> wrote:
> 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 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, but not Clang. I guess it's
probably fine to fix the Clang C++ include path without introducing new
variable bindings. Sorry for the mistake.
In a later message, Danny wrote:
> mrustc 0.9 supports bootstrapping Rust 1.29.0.
That's great news :)
Thank you!
Mark
next prev parent reply other threads:[~2019-11-07 19:54 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 [this message]
2019-10-29 15:37 ` Mathieu Othacehe
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=87lfsrihua.fsf@netris.org \
--to=mhw@netris.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/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.