The default build output is very terse. Add -d+2 (ie "Show commands
as they are executed") to BJAM_OPTS to make the do_compile logs more
informative.
Also add -q (ie "Stop at first error") to BJAM_OPTS and fix typo in
comments.
Signed-off-by: Andre McCurdy
---
On 24 February 2016 at 16:20, Martin Jansa wrote:
> distutils.errors.DistutilsError: Could not find suitable distribution for
> Requirement.parse('pbr>=1.3')
>
Missing DEPENDS?
Ross
--
___
Openembedded-core mailing list
The versioned gstreamer1.0-libav recipe includes --ranlib in
LIBAV_EXTRA_CONFIGURE_COMMON_ARG, but the git recipe does not.
It appears to be a historical mistake.
Signed-off-by: Andre McCurdy
---
meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_git.bb | 1 +
1 file
Andre McCurdy (4):
gstreamer1.0-libav_git: add --ranlib option to
LIBAV_EXTRA_CONFIGURE_COMMON_ARG
gstreamer1.0-libav: move LIBAV_EXTRA_CONFIGURE_COMMON_ARG into .inc
gstreamer1.0.inc: add explicit PACKAGECONFIG init
gstreamer1.0-plugins-XXX: move inherit gettext into common .inc file
gstreamer1.0-plugins-base/good/bad/ugly.inc all independently inherit
gettext. Move into the common gstreamer1.0-plugins.inc include file.
Signed-off-by: Andre McCurdy
---
meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-bad.inc | 2 +-
Although gstreamer1.0.inc doesn't currently set any default
PACKAGECONFIG options, add explicit initialisation in order to
match the style / structure of the other gstreamer1.0 recipes.
Signed-off-by: Andre McCurdy
---
meta/recipes-multimedia/gstreamer/gstreamer1.0.inc | 2
The LIBAV_EXTRA_CONFIGURE_COMMON_ARG definition is now common to both
the git and the versioned gstreamer1.0-libav recipes, so move it into
gstreamer1.0-libav.inc
Signed-off-by: Andre McCurdy
---
meta/recipes-multimedia/gstreamer/gstreamer1.0-libav.inc | 7 +++
The original over-ride dates back to 2009:
http://git.openembedded.org/openembedded-core/commit/?id=43e94412c45b4b79485a64010c76d89b245bb235
There are no obvious issues seen now when building boost in thumb2
for Cortex A15.
Signed-off-by: Andre McCurdy
---
On 24 February 2016 at 15:27, wrote:
> +python () {
> +# If the cve-check class is inherited it is needed to populate the
> +# CVE database before checking the CVEs for all recipes.
> +pn = d.getVar("PN", True)
> +if pn.endswith("-native") and
Hi Aníbal,
On Mon, 22 Feb 2016 12:31:33 Aníbal Limón wrote:
> From: Aníbal Limón
>
> The SDKUpdateTest class test devtool sdk-update mechanism inside
> eSDK.
>
> The SDKUpdateTest class search for new sdk if not found uses
> the main one then it publish the eSDK into
Signed-off-by: Ross Burton
---
meta/classes/package.bbclass | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index 93b275c..ef80e50 100644
--- a/meta/classes/package.bbclass
+++
Signed-off-by: Ross Burton
---
meta/classes/uninative.bbclass | 64 +-
1 file changed, 38 insertions(+), 26 deletions(-)
diff --git a/meta/classes/uninative.bbclass b/meta/classes/uninative.bbclass
index 270c1b0..0ca59d0 100644
---
Signed-off-by: Ross Burton
---
meta/classes/uninative.bbclass | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/meta/classes/uninative.bbclass b/meta/classes/uninative.bbclass
index 7e225e6..270c1b0 100644
--- a/meta/classes/uninative.bbclass
Signed-off-by: Ross Burton
---
meta/classes/insane.bbclass| 3 +--
meta/classes/uninative.bbclass | 2 +-
meta/lib/oe/qa.py | 15 +--
3 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/meta/classes/insane.bbclass
Instead of setting S to a directory inside the tarball and B to another
directory inside the tarball, use the default value of S and set
AUTOTOOLS_SCRIPT_PATH to the right path to find configure.
Rebase two patches to reflect the change of patch root.
For some reason doing this results in the
From: Mariano Lopez
cve-check-tool is a program to for checking public CVEs.
This tool also seek to determine if a vulnerability has
been addressed by a patch.
The recipe also includes the do_populate_cve_db task
that will populate the database used by the tool.
From: Mariano Lopez
This series add the cve-check-tool recipe, a tool used to identify
potentially vulnerable software through version matching. It will
check if a vulnerability has been addressed by a patch.
Also add the new cve-check class that will add a task
From: Mariano Lopez
This class adds a new task for all the recipes to use
cve-check-tool in order to look for public CVEs affecting
the packages generated.
It is possible to use this class when building an image,
building a recipe, or using the "world" or
From: Mariano Lopez
This patch allows to select the directory for the
database used by cve-check-tool.
[YOCTO #7515]
Signed-off-by: Mariano Lopez
---
.../change_logic_cve_get_file_parent.patch | 45 ++
When running ext-sdk-prepare.py during sdk installation a check is done to
make sure no tasks would run that aren't provided by the "leaf" recipes
specified in SDK_INSTALL_TARGETS.
However sometimes an image recipe can cause other images to be created
such as an initramfs. So make sure those
On Wednesday, February 24, 2016 3:02 PM, Paul Eggleton said:
> On Wed, 24 Feb 2016 22:59:13 Radzykewycz, T wrote:
> > On Wednesday, February 24, 2016 2:52 PM, Paul Eggleton said:
> > > On Wed, 24 Feb 2016 16:33:04 Robert P. J. Day wrote:
> > > > Quoting
On Wed, 24 Feb 2016 22:59:13 Radzykewycz, T wrote:
>
>
> On Wednesday, February 24, 2016 2:52 PM, Paul Eggleton said:
> > On Wed, 24 Feb 2016 16:33:04 Robert P. J. Day wrote:
> > > Quoting Christopher Larson :
> > > > All appends that
On Wednesday, February 24, 2016 2:52 PM, Paul Eggleton said:
> On Wed, 24 Feb 2016 16:33:04 Robert P. J. Day wrote:
> > Quoting Christopher Larson :
> > > All appends that apply to a given recipe will be applied to that recipe.
> > >
On Wed, Feb 24, 2016 at 6:52 AM, Joshua Lock wrote:
> ---
> meta/recipes-extended/hardlink/hardlink_0.3.0.bb | 19 +++
> 1 file changed, 19 insertions(+)
> create mode 100644 meta/recipes-extended/hardlink/hardlink_0.3.0.bb
>
> diff --git
On Wed, 24 Feb 2016 16:33:04 Robert P. J. Day wrote:
> Quoting Christopher Larson :
> > All appends that apply to a given recipe will be applied to that recipe.
> > Order is determined solely by layer priority.
>
>wait ... so *all* bbappend files that match a recipe will
- Avoid code duplication to handle -O, -O1 and -Os cases
- Consider the effective optimisation level only (avoids spurious
warnings if multiple optimisation flags are present).
- Prefix warnings with PN instead of hardcoding "glibc" (avoids
confusing warnings since the test is also applied
A bbappend basically concatenates to the recipe in bitgbake, so it can do
anything the recipe can do, within reason, so yes, use of filespath and
overrides works the way it's always worked with recipes.
On Wed, Feb 24, 2016 at 3:00 PM Robert P. J. Day
wrote:
>let's
Quoting Christopher Larson :
All appends that apply to a given recipe will be applied to that recipe.
Order is determined solely by layer priority.
wait ... so *all* bbappend files that match a recipe will be applied?
i'm embarrassed that i didn't know that, is that
Hello!
Does anyone know why host gdb (as built into a yocto sdk) does not have
working tab completion?
If I type "break wr" and then press tab, it does nothing. However, if I
type:
(gdb) complete b wr
b write
b wr...@got.plt
b write@plt
b writer.h
So, the completions are there, but something is
On 24 February 2016 at 14:52, Joshua Lock wrote:
> +do_compile () {
> + oe_runmake 'DESTDIR=${D}' 'PREFIX=${prefix}' BINDIR='${bindir}'
> +}
> +
> +do_install () {
> + oe_runmake install 'DESTDIR=${D}' 'PREFIX=${prefix}'
> BINDIR='${bindir}'
> +}
>
All appends that apply to a given recipe will be applied to that recipe.
Order is determined solely by layer priority.
On Wed, Feb 24, 2016 at 1:38 PM Robert P. J. Day
wrote:
>didn't immediately see this in the documentation anywhere, so what would
> happen in the
On 02/24/2016 02:51 PM, Paul Eggleton wrote:
> On Wed, 24 Feb 2016 11:35:25 Philip Balister wrote:
>> On 02/24/2016 11:06 AM, Trevor Woerner wrote:
>>> Ideally the work done here and the work done on meta-swupdate[1] would
>>> be somehow merged so people creating images/distros would only have to
didn't immediately see this in the documentation anywhere, so what would
happen in the following situation? say i have a layer that has three
different versions of a recipe:
* recipe-1.0.bb
* recipe-1.1.bb
* recipe-1.2.bb
if i want, i can extend each one with a .bbappend file:
*
From: Craig McQueen
This makes the resulting /etc/os-release file have valid shell
assignment syntax. This makes it loadable by a shell script, using the
'source' command:
source /etc/os-release
(From OE-Core master rev:
This is intended for after the imminent point release of course.
The following changes since commit 0c702756dd0009c4112028fbf2479a346867b32c:
build-appliance-image: Update to jethro head revision (2016-02-24 09:04:05
+)
are available in the git repository at:
On Wed, 24 Feb 2016 11:35:25 Philip Balister wrote:
> On 02/24/2016 11:06 AM, Trevor Woerner wrote:
> > Ideally the work done here and the work done on meta-swupdate[1] would
> > be somehow merged so people creating images/distros would only have to
> > learn and integrate one software update
On Wed, Feb 24, 2016 at 4:51 AM, Martin Jansa wrote:
> On Thu, Feb 18, 2016 at 11:21:23AM -0800, Andre McCurdy wrote:
>> Andre McCurdy (2):
>> libsoup-2.4: minor formatting improvements
>> libsoup-2.4: disable libsoup-gnome by default
>>
>>
On Wed, 2016-02-24 at 16:09 +, Lock, Joshua G wrote:
> On Wed, 2016-02-24 at 16:37 +0100, Patrick Ohly wrote:
> > Hello!
> >
> > I haven't had a chance to play with the actual code yet and I don't
> > know
> > yet when I'll be able to. Let me ask for some clarifications about
> > the
> >
> Dnia 24 luty 2016 o 17:35 Philip Balister napisał(a):
>
>
> On 02/24/2016 11:06 AM, Trevor Woerner wrote:
> > Ideally the work done here and the work done on meta-swupdate[1] would
> > be somehow merged so people creating images/distros would only have to
> > learn and
This includes a proper D-Bus service file for obexd in systems that do
not support systemd.
Signed-off-by: Javier Viguera
---
meta/recipes-connectivity/bluez5/bluez5.inc| 1 +
...-obexd-without-systemd-in-the-user-sessio.patch | 63 ++
2
This includes a proper D-Bus service file for obexd in systems that do
not support systemd.
Signed-off-by: Javier Viguera
---
meta/recipes-connectivity/bluez5/bluez5.inc| 1 +
...-obexd-without-systemd-in-the-user-sessio.patch | 63 ++
2
On 02/24/2016 03:55 AM, Alexander Kanavin wrote:
> On 02/16/2016 05:55 PM, akuster808 wrote:
>
>>> Yes, which means that jethro (which has 2.8.5) needs the same update.
>>
>> there is a bug open for that 8877. there are a huge number of CVE's that
>> need fixing.
>
> I wrote a comment in that
On Tue, 2016-02-23 at 16:18 -0600, Alex Franco wrote:
> I tested this with builds in my workstation and (local, internal)
> autobuilder, where TEST_SUITES is *not* specified in local.conf, so
> the
> TEST_SUITES are taken from the DEFAULT_TEST_SUITES variable for each
> image, which makes the
On 02/24/2016 11:06 AM, Trevor Woerner wrote:
> Ideally the work done here and the work done on meta-swupdate[1] would
> be somehow merged so people creating images/distros would only have to
> learn and integrate one software update solution, instead of having to
> evaluate and choose between the
Hi Winiston,
On Wed, Feb 24, 2016 at 06:20:14PM +0530, winis...@futuraautomation.com wrote:
> --
>Hi,
>
> I can build yocto image for arm based product like AM437x-evm using yocto
> project. I want to add third party software(Navit) to my image.
>
> How can I add the third party software to
On Wed, 2016-02-24 at 16:37 +0100, Patrick Ohly wrote:
> Hello!
>
> I haven't had a chance to play with the actual code yet and I don't
> know
> yet when I'll be able to. Let me ask for some clarifications about
> the
> approach first anyway.
>
> On Wed, 2016-02-24 at 14:52 +, Joshua Lock
On Wed, Feb 24, 2016 at 02:04:13PM +0100, Martin Jansa wrote:
> On Mon, Feb 22, 2016 at 08:35:02AM -0500, Derek Straka wrote:
> > Signed-off-by: Derek Straka
After fixing the download issue, I can see another error, which has the same
root cause (various fetch failures from my
Ideally the work done here and the work done on meta-swupdate[1] would
be somehow merged so people creating images/distros would only have to
learn and integrate one software update solution, instead of having to
evaluate and choose between the two (or more?).
[1]
Hello!
I haven't had a chance to play with the actual code yet and I don't know
yet when I'll be able to. Let me ask for some clarifications about the
approach first anyway.
On Wed, 2016-02-24 at 14:52 +, Joshua Lock wrote:
> Approach:
> An image that inherits the swupd-image bbclass will
Per os-release(5) the VERSION_ID field should be:
a lower-case string (mostly numeric, no spaces or other characters
outside of 0-9, a-z, ".", "_" and "-")
Do some string manipulation to try and ensure the VERSION_ID field
we write is valid.
Signed-off-by: Joshua Lock
This is useful for debugging swupd generated artefacts on the build
host i.e. `swupd hashdump`
Signed-off-by: Joshua Lock
---
meta/recipes-devtools/swupd/swupd-client_2.87.bb | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
From: Mariano Lopez
This commit adds the Clear Linux client updater.
This is experimental and bleeding edge, including the comments on the recipe.
Signed-off-by: Mariano Lopez
Signed-off-by: Joshua Lock
---
This class takes care of generating appropriate inputs for the swupd-server
to process, specifically the separate 'chroot'-like directory structures that
swupd-server expects to represent bundles.
It will then use swupd-server to process these 'chroot'-like directories into
update artefacts that
swup-client tries to call out to certain helper scripts during an update:
* before the update clr_pre_update.sh is called
* after the update systemdboot_updater.sh and kernel_updater.sh are called
* the systemd update-triggers.target is restarted once the update is complete
Clear Linux, the
---
meta/recipes-devtools/rsync/rsync_3.1.2.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/rsync/rsync_3.1.2.bb
b/meta/recipes-devtools/rsync/rsync_3.1.2.bb
index 71c2045..7237f43 100644
--- a/meta/recipes-devtools/rsync/rsync_3.1.2.bb
+++
The oe-swupd-helpers package provides scripts and units that swupd-client
calls before, during and after the update process.
Signed-off-by: Joshua Lock
---
meta/recipes-devtools/swupd/swupd-client_2.87.bb | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff
Our initial strategy to generate bundles for consumption by swupd
is to generate images which contain the base image (os-core) plus
the additional contents of the bundle, then prune out the core
contents. By generating images in this manner we hope to accomodate
packages which modify the rootfs
Include some patches to remove hard-coded state directory and backport some
fixes.
Signed-off-by: Joshua Lock
---
...S-to-take-the-state-data-dir-as-an-argume.patch | 782 +
...argv-helper-for-safer-calls-to-system-uti.patch | 133
---
meta/recipes-extended/hardlink/hardlink_0.3.0.bb | 19 +++
1 file changed, 19 insertions(+)
create mode 100644 meta/recipes-extended/hardlink/hardlink_0.3.0.bb
diff --git a/meta/recipes-extended/hardlink/hardlink_0.3.0.bb
b/meta/recipes-extended/hardlink/hardlink_0.3.0.bb
This series provides an initial set of changes to enable integration of the
swupd (https://clearlinux.org/features/software-update) software updater into an
image.
The changes are in the relatively early stages but I am hoping to land this work
before the M3 feature freeze so that the 2.1 release
On Wed, Feb 24, 2016 at 03:28:16PM +0200, Alexander Kanavin wrote:
> On 02/24/2016 03:16 PM, Martin Jansa wrote:
>
> > The distro needs to set ARM_INSTRUCTION_SET to "thumb" in order to enable
> > actually using this TUNE_FEATURE.
> >
> > With recent improvements in tune files you should clearly
On 02/24/2016 03:16 PM, Martin Jansa wrote:
The distro needs to set ARM_INSTRUCTION_SET to "thumb" in order to enable
actually using this TUNE_FEATURE.
With recent improvements in tune files you should clearly see that
default qemuarm builds are using TUNE_PKGARCH without "t" in it which
means
On Mon, Dec 14, 2015 at 08:03:47PM +0100, Martin Jansa wrote:
> This time full build (testing all recipes available in "my world" - 2503
> recipes), it took record-breaking 25days to finish.
>
> Complete log:
> http://logs.nslu2-linux.org/buildlogs/oe/world/log.dependencies.20151120_144802.log/
>
On Wed, Feb 24, 2016 at 02:34:32PM +0200, Alexander Kanavin wrote:
> On 02/24/2016 03:55 AM, Martin Jansa wrote:
> > Fails to build for qemuarm when thumb is enabled.
> >
> > Why was:
> > ARM_INSTRUCTION_SET = "arm"
> >
> > removed in
> >
On Thu, Feb 18, 2016 at 11:21:23AM -0800, Andre McCurdy wrote:
> Andre McCurdy (2):
> libsoup-2.4: minor formatting improvements
> libsoup-2.4: disable libsoup-gnome by default
>
> meta/recipes-support/libsoup/libsoup-2.4_2.52.2.bb | 20 +---
> 1 file changed, 9
Hi,
I can build yocto image for arm based product like AM437x-evm using yocto
project. I want to add third party software(Navit) to my image.
How can I add the third party software to my image ?. Can you provide me the
steps to integrate third party software with yocto image ?
Note: Navit is
On 02/24/2016 03:55 AM, Martin Jansa wrote:
Fails to build for qemuarm when thumb is enabled.
Why was:
ARM_INSTRUCTION_SET = "arm"
removed in
http://git.openembedded.org/openembedded-core/commit/?id=77dbf07293df15cd5473422abd678930d6277bb0
without checking if it works?
That line has no
From: He Zhe
Rename do_kernel_link_vmlinux to do_kernel_link_images and make a
symbol link to vmlinuz(if exists) for reference in arch/$arch/boot
directory.
Signen-off-by: He Zhe
---
meta/classes/kernel.bbclass | 13 -
From: He Zhe
Add KERNEL_IMAGETYPES to support building packaging and installing
multi types of kernel images, such as zImage uImage, at one time.
KERNEL_IMAGETYPE and KERNEL_ALT_IMAGETYPE work as before.
Signed-off-by: He Zhe
---
From: He Zhe
v1 to v2:
- Change KERNEL_OUTPUT to KERNEL_OUTPUT_DIR and update comments
- Update related doc files
- Replace all KERNEL_ALT_IMAGETYPEs with KERNEL_IMAGETYPES
- Link built vmlinuz to boot directory for reference
v2 to v3:
- Merge existing
On 02/16/2016 05:55 PM, akuster808 wrote:
Yes, which means that jethro (which has 2.8.5) needs the same update.
there is a bug open for that 8877. there are a huge number of CVE's that
need fixing.
I wrote a comment in that bug, but I think it bears repeating here:
Please read this, it's a
On Tue, 2016-02-23 at 18:23 +, Burton, Ross wrote:
>
> On 23 February 2016 at 18:01, Christopher Larson > wrote:
> > db isn't the only recipe doing that. The fetcher unpack method
> > knows where it's unpacking to, I think if anyone should be clearing
> > out the
[YOCTO #9161]
Signed-off-by: Robert Yang
---
meta/classes/sanity.bbclass | 12
1 file changed, 12 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 466eb49..edf49da 100644
--- a/meta/classes/sanity.bbclass
+++
* The vm image(hdddirect, vmdk, qcow2, vdi) and live image (hddimg, iso)
couldn't be built together because the following vars settings are
conflicted:
- SYSLINUX_ROOT (/dev/sda2 vs /dev/ram0)
- LABELS (boot vs boot install)
- INITRD (None vs live install)
- SYSLINUX_CFG (see above)
The IS_VM was used for making menus for vmdk, vdi and qcow2, except
hddimg, there is no reason to not make menus for hddimg, so drop it.
Signed-off-by: Robert Yang
---
meta/classes/boot-directdisk.bbclass | 12
1 file changed, 4 insertions(+), 8
No one uses it.
Signed-off-by: Robert Yang
---
meta/classes/boot-directdisk.bbclass |1 -
meta/classes/image-live.bbclass |1 -
2 files changed, 2 deletions(-)
diff --git a/meta/classes/boot-directdisk.bbclass
b/meta/classes/boot-directdisk.bbclass
Hello,
These patches can make vm and live images build together, and also make
the images easier to use.
I'd like to combine the following classes if you are fine with it:
* boot-directdisk.bbclass and image-vm.bbclass into image-vm.bbclass.
They are used for making vm images.
*
On 2016年02月24日 01:10, Burton, Ross wrote:
On 23 February 2016 at 17:01, Burton, Ross > wrote:
The *amazing* BB_VERBOSE_LOGS option (set to 1 in local.conf to
get all shell scripts to do set -x) tells me this is due to
missing
78 matches
Mail list logo