openembedded-core.git/meta/recipes-core, branch uninative-1.4

buildtools/uninative-tarball: Fix deployment overlap issues

2016-09-23T17:06:03+00:00

We still have problems where deploying SDKMACHINE=i686 can cause removal
of SDKMACHINE=x86_64 artefacts.

The reason is that x86_64 is a BUILD_ARCH as well as an SDK_ARCH and
the manifest namespaces overlap. To fix this, set PACKAGE_ARCH and
the stamp-extra-into to include SDK_OS. SDK_OS may not be entirely correct
but it is what sstate.bbclass uses for nativesdk and fixing that is
a separate issue.

This is confirmed to resolve artefact problems on the AB which have been
delaying a new uninative release.

Signed-off-by: Richard Purdie

buildtools-tarball: improve stamp independence

2016-09-23T13:53:55+00:00

buildtools-tarball shouldn't be regenerated when MACHINE changes,
nor should variants for other SDKMACHINE be removed from the deploy
directory when SDKMACHINE changes.

Remove target architecture dependencies so that deploy artefacts
can overlap.

Signed-off-by: Joshua Lock 
Signed-off-by: Richard Purdie

systemd: fix indentation

2016-09-22T10:08:22+00:00

Signed-off-by: Maciej Borzecki 
Signed-off-by: Ross Burton

uninative-tarball: Make stamp independent

2016-09-21T23:24:51+00:00

The uninative tarball only contains nativesdk compoents. It should
not get regenerated when MACHINE changes for example. Currently its
sstate arch is also incorrect so changing SDKMACHINE results in other
variants being removed from the deploy directory.

This patch removes the target architecture dependencies so that
deploy artefacts can overlap and it doesn't continually rebuild. This
also fixes various autobuilder/release artefact issues we're having
as a result of these issues.

Signed-off-by: Richard Purdie

buildtools-tarball: add SDKMACHINE to stamps-extra-info

2016-09-21T20:59:29+00:00

Otherwise the stamps for x86-64 and i686 uninative tarballs match
and we can't deploy both to the DEPLOYDIR.

Signed-off-by: Joshua Lock 
Signed-off-by: Richard Purdie

uninative-tarball: add SDKMACHINE to stamps-extra-info

2016-09-21T17:12:03+00:00

Otherwise the stamps for x86-64 and i686 uninative tarballs match
and we can't deploy both to the DEPLOYDIR.

Signed-off-by: Joshua Lock 
Signed-off-by: Richard Purdie

dropbear: deterministic selection of system -vs- bundled libtom libs

2016-09-19T22:57:20+00:00

Dropbear will use system versions of libtommath and libtomcrypt if
available. To make builds deterministic, add a PACKAGECONFIG option
to choose system libs or force use of the bundled versions.

Note that currently there are no libtommath or libtomcrypt recipes
in oe-core, so default to using the bundled versions.

Signed-off-by: Andre McCurdy 
Signed-off-by: Richard Purdie

dropbear: fix -ltomcrypt -ltommath order when using system libtom libs

2016-09-19T22:57:20+00:00

To prevent build failures when using system libtom libraries and
linking with --as-needed, LIBTOM_LIBS should be in the order
-ltomcrypt -ltommath, not the other way around, ie libs should be
prepended to LIBTOM_LIBS as they are found, not appended.

Note that LIBTOM_LIBS is not used when linking with the bundled
libtom libs.

Signed-off-by: Andre McCurdy 
Signed-off-by: Richard Purdie

build-appliance-image: Create image in correct location

2016-09-19T07:58:04+00:00

Due to the recipe now using variable IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE,
the final Build Appliance image ended up being created in a wrong location.

This patch assures the final ZIP image is created in identical location as before:

   tmp/deploy/images//Yocto_Build_Apliance.zip

[YOCTO#10274]

Signed-off-by: Juro Bystricky 
Signed-off-by: Richard Purdie

util-linux: Disable bfs support

2016-09-16T14:15:33+00:00

Disable building of mkfs.bfs, which is used to create
BFS file-systems used by SCO UnixWare.  This is highly
unlikely to be utilized and there are otherwise no
references to 'bfs' throughout the rest of the tree.

Signed-off-by: Patrick Williams 
Signed-off-by: Richard Purdie