From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add llvm-3.6.0 and clang-3.6.0
Date: Mon, 02 Mar 2015 12:09:54 -0500 [thread overview]
Message-ID: <87lhjfz5p9.fsf@netris.org> (raw)
In-Reply-To: <871tl71pjm.fsf@netris.org> (Mark H. Weaver's message of "Mon, 02 Mar 2015 08:45:17 -0500")
Mark H Weaver <mhw@netris.org> writes:
> This updates llvm and clang to 3.6.0, while keeping 3.5.0 available as
> well. It creates a new procedure 'clang-from-llvm' that does the
> obvious thing. I want to keep 3.5.0 around for purposes of testing
> Guile with various versions of clang.
>
> I've verified that the 3.5.0 packages generate the same derivations as
> before, but have not yet finished building 3.6.0 to make sure it works.
They built successfully on my i686 system, so I went ahead and pushed
this.
Mark
prev parent reply other threads:[~2015-03-02 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 13:45 [PATCH] gnu: Add llvm-3.6.0 and clang-3.6.0 Mark H Weaver
2015-03-02 17:09 ` Mark H Weaver [this message]
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=87lhjfz5p9.fsf@netris.org \
--to=mhw@netris.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 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).