From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46637) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d8Omr-00043p-Ax for guix-patches@gnu.org; Wed, 10 May 2017 06:24:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d8Omo-000473-6R for guix-patches@gnu.org; Wed, 10 May 2017 06:24:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60680) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d8Omo-00046z-3I for guix-patches@gnu.org; Wed, 10 May 2017 06:24:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1d8Omn-0001tE-R7 for guix-patches@gnu.org; Wed, 10 May 2017 06:24:01 -0400 Subject: bug#25879: [PATCH] gnu: Add LLVM and CLANG 3.9.1. Resent-Message-ID: References: <87shn12p2i.fsf@gnu.org> <87k28180ob.fsf@gnu.org> <87d1dskjdh.fsf@gnu.org> <8737eosvgb.fsf@gnu.org> <20170307212411.GA29363@mail.thebird.nl> <87bmr1i6l3.fsf@elephly.net> <87inl9gpvu.fsf@gnu.org> <877f1phvox.fsf@elephly.net> From: Ricardo Wurmus In-reply-to: Date: Wed, 10 May 2017 12:23:25 +0200 Message-ID: <874lwthuxu.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Roel Janssen Cc: 25879@debbugs.gnu.org Roel Janssen writes: > Ricardo Wurmus writes: > >> Roel Janssen writes: >> >>> Ricardo Wurmus writes: >>> >>>> Pjotr Prins 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. > > So, is it OK to push the patch as-is then? Yes, please! :) If you can, it would be good to investigate if current users of 3.8 could be built with 3.9, but this doesn’t have to block this patch in my opinion. If in fact all users of 3.8 can be built with 3.9 without problems you can make the change in a follow-up commit. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net