unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Roel Janssen <roel@gnu.org>
Cc: 25879@debbugs.gnu.org
Subject: bug#25879: [PATCH] gnu: Add LLVM and CLANG 3.9.1.
Date: Wed, 10 May 2017 12:07:10 +0200	[thread overview]
Message-ID: <877f1phvox.fsf@elephly.net> (raw)
In-Reply-To: <87inl9gpvu.fsf@gnu.org>


Roel Janssen <roel@gnu.org> writes:

> Ricardo Wurmus writes:
>
>> 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?
>
> I think the idea was to upgrade, instead of have this newer version next
> to the current version.  The upgrade involves a lot of rebuilding, and I
> am stuck at compiling 'dub' with 3.9.1.
>
> If we can instead apply this patch as (having both 3.8.1 and 3.9.1), we
> can push it, and after that add the darktable patch as well.

I think it’s fine to have multiple versions of LLVM + Clang around,
especially considering that in my experience many dependent projects
won’t build with later versions without adjustments.  (RStudio, for
example, still insists on the oldest version of Clang that we offer, and
it crashes with later versions.)

It would be good to keep an eye on this, though, to make sure that we
don’t provide outdated versions that have no users and no maintainer.

--
Ricardo

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

  reply	other threads:[~2017-05-10 10:08 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         ` bug#25879: [PATCH] gnu: Add LLVM and CLANG 3.9.1 Ricardo Wurmus
2017-05-10  6:57           ` Roel Janssen
2017-05-10 10:07             ` Ricardo Wurmus [this message]
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

  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=877f1phvox.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=25879@debbugs.gnu.org \
    --cc=roel@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).