• Joseph Rushton Wakeling (8/8) Dec 30 2013 Anyone know what the official status of llvm 3.4 is? The website
• Dwhatever (6/14) Dec 30 2013 I just used the llvm trunk together with LDC a week a ago and it
• Kai Nacke (8/14) Jan 01 2014 Currently, it is broke (changed or new library). I'll fix this
• Joseph Rushton Wakeling (3/8) Jan 01 2014 I'm assuming that more than anything it's just holiday-induced
• Kai Nacke (5/14) Jan 06 2014 The LLVM page now lists 3.4 as latest release.
• Joseph Rushton Wakeling (2/3) Jan 08 2014 Ta. :-)
• Kai Nacke (8/10) Jan 02 2014 Ok, this was a problem of my build environment. You can use LLVM

"Joseph Rushton Wakeling" <joseph.wakeling webdrake.net> writes:

Anyone know what the official status of llvm 3.4 is? The website 
continues to list 3.3 as the current release while now indicating 
that 3.5 is the upcoming release; there's nothing on the 
announcements mailing list archive, but the development release 
of Ubuntu has landed 3.4 packages with release version numbers, 
not rc.

Really I'm just wondering which llvm-dev I should use for my next 
LDC build :-P

"Dwhatever" <not real.com> writes:

On Monday, 30 December 2013 at 08:42:37 UTC, Joseph Rushton 
Wakeling wrote:
 Anyone know what the official status of llvm 3.4 is? The 
 website continues to list 3.3 as the current release while now 
 indicating that 3.5 is the upcoming release; there's nothing on 
 the announcements mailing list archive, but the development 
 release of Ubuntu has landed 3.4 packages with release version 
 numbers, not rc.

 Really I'm just wondering which llvm-dev I should use for my 
 next LDC build :-P

I just used the llvm trunk together with LDC a week a ago and it 
worked fine.

I've no idea why they removed 3.4 on the llvm site. Maybe it's 
just not fully updated yet.

"Kai Nacke" <kai redstar.de> writes:

Hi Josepd!

On Monday, 30 December 2013 at 10:05:18 UTC, Dwhatever wrote:
 On Monday, 30 December 2013 at 08:42:37 UTC, Joseph Rushton 
 Wakeling wrote:

 I just used the llvm trunk together with LDC a week a ago and 
 it worked fine.

Currently, it is broke (changed or new library). I'll fix this 
soon.

 I've no idea why they removed 3.4 on the llvm site. Maybe it's 
 just not fully updated yet.

I think that's it. There was no announcement on the devel mailing 
list.

Regards,
Kai

"Joseph Rushton Wakeling" <joseph.wakeling webdrake.net> writes:

On Wednesday, 1 January 2014 at 15:40:07 UTC, Kai Nacke wrote:
 On Monday, 30 December 2013 at 10:05:18 UTC, Dwhatever wrote:
 I've no idea why they removed 3.4 on the llvm site. Maybe it's 
 just not fully updated yet.

 I think that's it. There was no announcement on the devel 
 mailing list.

I'm assuming that more than anything it's just holiday-induced 
crossed wires :-)

"Kai Nacke" <kai redstar.de> writes:

On Wednesday, 1 January 2014 at 20:21:35 UTC, Joseph Rushton 
Wakeling wrote:
 On Wednesday, 1 January 2014 at 15:40:07 UTC, Kai Nacke wrote:
 On Monday, 30 December 2013 at 10:05:18 UTC, Dwhatever wrote:
 I've no idea why they removed 3.4 on the llvm site. Maybe 
 it's just not fully updated yet.

 I think that's it. There was no announcement on the devel 
 mailing list.

 I'm assuming that more than anything it's just holiday-induced 
 crossed wires :-)

The LLVM page now lists 3.4 as latest release.

Regards,
Kai

"Joseph Rushton Wakeling" <joseph.wakeling webdrake.net> writes:

On Monday, 6 January 2014 at 15:58:14 UTC, Kai Nacke wrote:
 The LLVM page now lists 3.4 as latest release.

Ta. :-)

"Kai Nacke" <kai redstar.de> writes:

On Wednesday, 1 January 2014 at 15:40:07 UTC, Kai Nacke wrote:
 Currently, it is broke (changed or new library). I'll fix this 
 soon.

Ok, this was a problem of my build environment. You can use LLVM 
3.4 or LLVM trunk without problems.
There is a known failure with LLVM trunk - it is possible an 

(https://github.com/ldc-developers/ldc/issues/546).

Regards,
Kai