On Wed, Oct 14, 2015 at 08:48:51PM +0200, Jens Rehsack wrote: > > llvm introduced new JIT technology MCJIT with llvm 3.4 and fixes ARM in 3.5 > (see > http://llvm.org/releases/3.5.2/docs/ReleaseNotes.html#changes-to-the-arm-backend). > > Ensure JIT is built with llvm
I'm tempted to leave this one after jethro is branched, unless default LLVM_RELEASE is updated in oe-core/jethro mesa as well. Otherwise everybody will need to set LLVM_RELASE in their mesa bbappend or we'll need to bbappend it in meta-oe. What others think? And was this tested with mesa or just with java? Regards, > > Signed-off-by: Jens Rehsack <[email protected]> > --- > meta-oe/recipes-core/llvm/llvm.inc | 8 +--- > ...r-output-from-configure-if-CFLAGS-is-set-.patch | 52 > ---------------------- > .../{llvm3.3 => llvm3.5}/arm_fenv_uclibc.patch | 0 > .../llvm/{llvm3.3_3.3.bb => llvm3.5_3.5.2.bb} | 11 +++-- > 4 files changed, 9 insertions(+), 62 deletions(-) > delete mode 100644 > meta-oe/recipes-core/llvm/llvm3.3/Remove-error-output-from-configure-if-CFLAGS-is-set-.patch > rename meta-oe/recipes-core/llvm/{llvm3.3 => llvm3.5}/arm_fenv_uclibc.patch > (100%) > rename meta-oe/recipes-core/llvm/{llvm3.3_3.3.bb => llvm3.5_3.5.2.bb} (71%)
signature.asc
Description: Digital signature
-- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
