On 14/07/14 13:58, Cyril Brulebois wrote: > Sylvestre Ledru <sylvestre@debian.org> (2014-07-14): >> Could you update the clang build dep from 3.3 to 3.4? >> It prevents the removal of llvm &clang 3.3. > > The important part is not 3.3 going away; it's about making sure stuff > still works fine with 3.4 *first*. Whenever old packages go away really > shouldn't be a goal on its own… It's okay, I think we can do this, or at least I am in favour of trying. IMHO you could raise the severity of this bug to serious. (This will be much, much easier than in the wheezy cycle where older GCC versions went away with *hundreds* of reverse deps still using it, and kfreebsd never having been tested with anything newer). We like to use the same version of Clang that upstream used to build the kernels, to be safe. So for now, kfreebsd-10 uses clang-3.3 which is what FreeBSD 10.0 was released with. kfreebsd-11, and the 10-STABLE branch which will become 10.1, have both jumped to clang-3.4 already. That suggests 10.0 is very likely to work with clang-3.4, and 10-STABLE already been heavily tested with it, perhaps only needing some small changes backported to 10.0, if anything. But anyway, some of us would prefer to actually release jessie with 10.1, in which case that would definitely be built with clang-3.4. See [🔎] alpine.LNX.2.00.1407130920110.13442@contest.felk.cvut.cz">http://[🔎] alpine.LNX.2.00.1407130920110.13442@contest.felk.cvut.cz The timing of that would be very tight though, so we're likely to have 10.0 in either jessie or sid up until about October. Regards, -- Steven Chamberlain steven@pyro.eu.org
Attachment:
signature.asc
Description: OpenPGP digital signature