all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: 25879@debbugs.gnu.org
Subject: bug#25879: [PATCH] gnu: Add LLVM and CLANG 3.9.1.
Date: Wed, 10 May 2017 08:11:52 +0200	[thread overview]
Message-ID: <87bmr1i6l3.fsf@elephly.net> (raw)
In-Reply-To: <20170307212411.GA29363@mail.thebird.nl>


Pjotr Prins <pjotr.public12@thebird.nl> writes:

> On Tue, Mar 07, 2017 at 09:06:28PM +0100, Ludovic Courtès wrote:
>> > Well, actually, this is just the latest release, so maybe I should
>> > update the 3.8.1 recipe to3.9.1 instead.  WDYT?
>>
>> If the other users of LLVM and Clang (as per ‘guix refresh -l llvm’) can
>> cope with it, upgrading sounds better indeed.  Could you check if that
>> is the case?
>
> With LLVM it is probably a good idea to keep the major versions as
> packages tend to lag after latest. Many compiler writers are a bit
> behind and sometimes people want to use older compilers (like with
> Julia).

I agree.

@Roel: I see that this patch hasn’t been pushed yet.  Is there anything
missing or was it just forgotten?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

       reply	other threads:[~2017-05-10  6:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87shn12p2i.fsf@gnu.org>
     [not found] ` <87k28180ob.fsf@gnu.org>
     [not found]   ` <87d1dskjdh.fsf@gnu.org>
     [not found]     ` <8737eosvgb.fsf@gnu.org>
     [not found]       ` <20170307212411.GA29363@mail.thebird.nl>
2017-05-10  6:11         ` Ricardo Wurmus [this message]
2017-05-10  6:57           ` bug#25879: [PATCH] gnu: Add LLVM and CLANG 3.9.1 Roel Janssen
2017-05-10 10:07             ` Ricardo Wurmus
2017-05-10 10:17               ` Roel Janssen
2017-05-10 10:23                 ` Ricardo Wurmus
2017-05-10 13:44                   ` Roel Janssen
2017-05-10 13:54                     ` Ricardo Wurmus

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=87bmr1i6l3.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=25879@debbugs.gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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.