On 2016-07-06 06:54, Efraim Flashner wrote:
On Wed, Jul 06, 2016 at 06:55:56AM +0200, Ricardo Wurmus wrote:
Roel Janssen writes:
>>From 451d93eaaab6166e38e33f0556fe40f83afefc5c Mon Sep 17 00:00:00 2001
> From: brainiarc7
> Date: Tue, 5 Jul 2016 22:42:24 +0200
> Subject: [PATCH] gnu: Add LLVM
On Wed, Jul 06, 2016 at 06:55:56AM +0200, Ricardo Wurmus wrote:
>
> Roel Janssen writes:
>
> >>From 451d93eaaab6166e38e33f0556fe40f83afefc5c Mon Sep 17 00:00:00 2001
> > From: brainiarc7
> > Date: Tue, 5 Jul 2016 22:42:24 +0200
> > Subject: [PATCH] gnu: Add LLVM 3.8.
> >
> > * gnu/packages/llvm
Roel Janssen writes:
>>From 451d93eaaab6166e38e33f0556fe40f83afefc5c Mon Sep 17 00:00:00 2001
> From: brainiarc7
> Date: Tue, 5 Jul 2016 22:42:24 +0200
> Subject: [PATCH] gnu: Add LLVM 3.8.
>
> * gnu/packages/llvm.scm (llvm-3.8): New variable.
> * gnu/packages/llvm.scm (clang-runtime-3.8): New
Does everyone agree that the proposed patch is fine?
Dennis Mungai writes:
> Roel, you may push.
>
> Also, I prefer the name Dennis Mungai.
>
> :-)
>
> On 5 July 2016 at 23:48, Roel Janssen wrote:
>> Hello Dennis,
>>
>> Thanks for your work on LLVM-3.8. I see a couple of things:
>> - We try to
Roel, you may push.
Also, I prefer the name Dennis Mungai.
:-)
On 5 July 2016 at 23:48, Roel Janssen wrote:
> Hello Dennis,
>
> Thanks for your work on LLVM-3.8. I see a couple of things:
> - We try to keep lines within 80 columns.
> - libffi and zlib should be inputs instead of native-inputs.
Hello Dennis,
Thanks for your work on LLVM-3.8. I see a couple of things:
- We try to keep lines within 80 columns.
- libffi and zlib should be inputs instead of native-inputs.
- zlib is both a license and a package, so the licenses should be
prefixed.
I created a new patch for you addressing th
Hello,
See the corrected patch below, comments have been corrected.
>From 38643acf50749212a4455d15a1729002d6dfa04a Mon Sep 17 00:00:00 2001
From: brainiarc7
Date: Thu, 30 June 2016 20:43:13 +0300
Subject: [PATCH] Add LLVM 3.8 to GNU Guix
---
gnu/packages/llvm.scm | 39
>From 38643acf50749212a4455d15a1729002d6dfa04a Mon Sep 17 00:00:00 2001
From: brainiarc7
Date: Thu, 30 June 2016 16:47:02 +0300
Subject: [PATCH] Add LLVM 3.8 to GNU Guix
---
gnu/packages/llvm.scm | 39 +++
1 file changed, 39 insertions(+)
diff --git a/gnu/pa
Hi!
Dennis Mungai skribis:
> I second Pjotr on this.
>
> There are always tools that will lag behind, and having multiple LLVM
> versions is a reasonable (and possibly unavoidable) compromise, for
> now.
>
> There may be problems with conflicts should a user install such
> pipelines with differi
I second Pjotr on this.
There are always tools that will lag behind, and having multiple LLVM
versions is a reasonable (and possibly unavoidable) compromise, for
now.
There may be problems with conflicts should a user install such
pipelines with differing LLVM and Clang combinations within the sa
On Sat, May 28, 2016 at 05:30:49PM +0200, Ludovic Courtès wrote:
> Hi!
>
> Another question: is there any use for all these versions, or should we
> instead just bump llvm/clang/clang-runtime to 3.8?
>
> LLVM 3.6 currently has only five users:
rdmd and ldc just got upgraded to LLVM 3.8 - we'll u
Hi Dennis,
Dennis Mungai skribis:
> I have made a few changes that should ensure a successful build of
> both clang and clang-runtime-3.8, by disabling test units from llvm
> 3.8 as they generated invalid targets for clang.
What’s your opinion on this:
> On 28 May 2016 at 18:30, Ludovic Courtè
Hello fellows,
I have made a few changes that should ensure a successful build of
both clang and clang-runtime-3.8, by disabling test units from llvm
3.8 as they generated invalid targets for clang.
Test and confirm that the patch fixes the issues highlighted above.
Thanks and regards,
Dennis.
Hi!
Another question: is there any use for all these versions, or should we
instead just bump llvm/clang/clang-runtime to 3.8?
LLVM 3.6 currently has only five users:
--8<---cut here---start->8---
$ GUIX_PACKAGE_PATH= guix refresh -l llvm@3.6
Building the foll
Eric Bavier writes:
> On 2016-05-26 15:44, Dennis Mungai wrote:
>> See corrected patch, as attached.
>
>> +(define-public clang-3.8
>> + (clang-from-llvm llvm-3.8 clang-runtime-3.8
>> +
>> >"1ybcac8hlr9vl3wg8s4v6cp0c0qgqnwprsv85lihbkq3vqv94504"))
>
> Did you successfully build
Yes, I did.
I'll inspect this shortly and give you feedback.
On 27 May 2016 at 17:09, Eric Bavier wrote:
> On 2016-05-26 15:44, Dennis Mungai wrote:
>>
>> See corrected patch, as attached.
>
>
>> +(define-public clang-3.8
>> + (clang-from-llvm llvm-3.8 clang-runtime-3.8
>> +
>> >"1ybcac8hlr9vl3
On 2016-05-26 15:44, Dennis Mungai wrote:
See corrected patch, as attached.
+(define-public clang-3.8
+ (clang-from-llvm llvm-3.8 clang-runtime-3.8
+
>"1ybcac8hlr9vl3wg8s4v6cp0c0qgqnwprsv85lihbkq3vqv94504"))
Did you successfully build clang 3.8 with this patch? I ask bec
See corrected patch, as attached.
On 26 May 2016 at 23:13, Roel Janssen wrote:
> Hello Dennis,
>
> Welcome and thank you for the patch.
>
> Dennis Mungai writes:
>
>> +(define-public llvm-3.8
>> + (package (inherit llvm)
>> +(version "3.8.0")
>> +(source
>> + (origin
>> + (me
Hello Dennis,
Welcome and thank you for the patch.
Dennis Mungai writes:
> +(define-public llvm-3.8
> + (package (inherit llvm)
> +(version "3.8.0")
> +(source
> + (origin
> + (method url-fetch)
> + (uri (string-append "http://llvm.org/releases/";
> +
19 matches
Mail list logo