Control: reassign -1 rustc Control: retitle -1 build against llvm 3.7 instead of 3.6
Hi, I built rustc nightly packages against the new llvm 3.7 package - see #796256 - and they work fine. So we don't need to fix llvm 3.6. Reassigning this bug just for bookkeeping; it's already fixed in the rustc packaging git repo. https://anonscm.debian.org/cgit/pkg-rust/rust.git/commit/?id=0fbc9e96fbf9bf9be9e9a3d10010254af52b447d X On 02/09/15 12:06, Ximin Luo wrote: > On 01/09/15 13:51, Ximin Luo wrote: >> On 01/09/15 13:32, Sylvestre Ledru wrote: >>> severity 797626 normal >>> thanks >>> >>> Le 01/09/2015 01:05, Ximin Luo a écrit : >>>> Source: llvm-toolchain-3.6 >>>> Severity: important >>>> Tags: upstream patch >>>> >>>> Dear Maintainer, >>>> >>>> Please apply the attached patch. The origin is: >>>> >>>> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20150622/282940.html >>>> >>>> and it is necessary to make later versions of rustc compile correctly, see >>>> >>>> https://github.com/rust-lang/rust/issues/26468 >>>> >>>> I have tested the patch against 1:3.6.2-1 and it applies cleanly with an >>>> offset. >>> I will see what I can do. Any idea if this is going to land in the 3.6 >>> upstream branch? >>> >> >> I'm not sure, I don't know what their release policy is like. >> >> BTW, I built the previous patch and the tests failed - it was only the first >> attempt at a patch on a mailing list. I've pulled the actual relevant LLVM >> commits, see the attached new patch. I'm building it again but it will take >> a few hours before I get the results. >> > > This didn't work either. But it looks like these patches have already been > applied in the 3.7 release. I should probably have just tried that first, > instead of trying to backport this... > > X > -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
