Re: [OE-core] [PATCH v2] uninative: rebuild uninative for gcc 4.8 and 4.9

This fails on the AB when generating a eSDK, eg http://errors.yoctoproject.org/Errors/Details/110635/ I suspect the cause is that the sstate is generated using the (eg) universal-4.9 name, but populate_sdk_ext still uses just "universal" when creating a mirror of the sstate archive. Ross On 8

[OE-core] [PATCH v2] uninative: rebuild uninative for gcc 4.8 and 4.9

Some c++ libraries fail to build if uninative is built with gcc 5.x and host gcc version is either 4.8 or 4.9. The issue should be solved by making separate uninative sstate directory structure sstate-cache/universal- for host gcc versions 4.8 and 4.9. This causes rebuilds of uninative if host

Re: [OE-core] [PATCH v2] uninative: rebuild uninative for gcc 4.8 and 4.9

On 27 October 2016 at 08:10, Ed Bartosh wrote: > +match = re.match(".* (\d\.\d)\.\d .*", output.split('\n')[0]) > Debian uses this string: gcc (Debian 4.9.2-10) 4.9.2 So your regex needs to be a bit more permissive, and it looks like grabbing the second number

[OE-core] [PATCH v2] uninative: rebuild uninative for gcc 4.8 and 4.9

Some c++ libraries fail to build if uninative is built with gcc 5.x and host gcc version is either 4.8 or 4.9. The issue should be solved by making separate uninative sstate directory structure sstate-cache/universal- for host gcc versions 4.8 and 4.9. This causes rebuilds of uninative if host