Bug 783677 - llvm 3.1 for april
Summary: llvm 3.1 for april
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: llvm
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michel Lind
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-21 17:15 UTC by MERCIER Jonathan
Modified: 2012-02-02 01:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-02-02 01:35:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description MERCIER Jonathan 2012-01-21 17:15:12 UTC
Hi,
like LLVM 3.1 will be released around april. It will be great if fedora 17 repo can follow upstream periodiaclly to 3.1

Thanks

Comment 1 Michel Lind 2012-02-02 01:35:58 UTC
Can't do -- as we've discussed previously, because LLVM is used in critical parts (e.g. for Mesa -- in fact, GNOME Shell 3.4's ability to run without 3D acceleration depends on this), we can't ship an upgraded LLVM unless upstream starts doing pre-release testing before our feature freeze. Which they have not.

Right now, with GCC 4.7.0 in Rawhide, we can't even build either LLVM 3.0 or LLVM trunk. LLVM 3.1 is definitely not a good idea at this stage.

Once F17 is branched and Rawhide is free-for-all again, I'd consider this, but even then, from experience many of the packages that build against LLVM only support stable releases, so there'll be an outcry when the LLVM snapshot lands. I think I'll actually ask rel-eng for a special tag for rebuilding the LLVM stack against the 3.1 pre-releases, and only land them in Rawhide once the major parts are ready.


Note You need to log in before you can comment on or make changes to this bug.