The buildtools build target needs two extra builds adding: SDKMACHINE=i586 bitbake uninative-tarball SDKMACHINE=x86_64 bitbake uninative-tarball We will start using uninative in the poky distro by default and will need to host a stable version of these binaries somewhere too.
Beth, can we get this in sooner rather than later? Publishing the artifacts alongside the other SDK bits would be key too.
Sure, the build is in, I just wanted to see exactly what is being produced before I go modifying PublishArtifacts.
All relevant branches are fixed.
I cannot find published the i686 files: http://autobuilder.yoctoproject.org/pub/nightly/20160215-1/toolchain/i686/ x86_64 are published: http://autobuilder.yoctoproject.org/pub/nightly/CURRENT/toolchain/x86_64/ Please indicate the correct link, if are published somewhere else.
We're only building them for nightly-x86-64. IIRC I don't thinkg we wanted them for nightly-x86
Hi Richard, Please help with a clarification: uninative-tarball should be built only for nightly-x86-64? (http://autobuilder.yoctoproject.org/pub/nightly/20160215-1/toolchain/x86_64/) For http://autobuilder.yoctoproject.org/pub/nightly/20160215-1/toolchain/i686/ are not built. BR, Bogdan
I think we should be building these with SDKMACHINE = "i686" and SDKMACHINE = "x86_64". Its eSDK which is x86_64 only. Reassign back to Beth to fix.
This is actually an issue with uninative.bbclass. UNINATIVE_TARBALL ?= "${BUILD_ARCH}-nativesdk-libc.tar.bz2" should be something like: UNINATIVE_TARBALL ?= "${BUILD_ARCH}-nativesdk-libc-${SDKMACHINE}.tar.bz2" I've got the conf producing both but the second build pass is stomping on the first.
Patch sent to make the uninative-tarball artifacts actually respect SDKMACHINE.
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/commit/?id=57f53ce20b066d1dd696096d0bb6d360af89ae7d
Verified on http://autobuilder.yoctoproject.org/pub/nightly/20160307-1/toolchain/