all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Roel Janssen <roel@gnu.org>
Cc: 25879-done@debbugs.gnu.org
Subject: bug#25879: [PATCH] gnu: Add LLVM and CLANG 3.9.1.
Date: Wed, 10 May 2017 15:54:44 +0200	[thread overview]
Message-ID: <87wp9ohl5n.fsf@elephly.net> (raw)
In-Reply-To: <87wp9okeqt.fsf@gnu.org>


Roel Janssen <roel@gnu.org> writes:

>>> So, is it OK to push the patch as-is then?
>>
>> Yes, please!  :)
>
> Pushed in 584da12dc71da745edb13bf748e832b77a0193d7.

Great!  Closing this bug.

>> 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.
>
> I am sure that at least 'c-reduce' does not build with 3.9.1.  So I
> think we'll need to take this on a per-program basis.  I'll see which
> ones can be built with 3.9.1.

Thanks for taking care of this!

-- 
Ricardo

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

      reply	other threads:[~2017-05-10 13:55 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
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 [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wp9ohl5n.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=25879-done@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 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.