The dependencies chain:
run-postinsts -> update-rc.d.bbclass -> initscripts -> update-alternatives.
The update-alternatives is provided by opkg-utils which is not allarch.
This caused a problem:
$ bitbake lib32-core-image-minimal
Both lib32-opkg-utils and opkg-utils would be built, but opkg-util
Fixed when DEBUG_BUILD = "1":
test-backface-culling.c:206:7: error: 'cull_front' may be used uninitialized in
this function [-Werror=maybe-uninitialized]
|validate_part (framebuffer,
|^
| cc1: some warnings being treated as errors
Signed-off-by: Robert Yang
---
...ce-culling.c-f
If a recipe needs to build some tool on the build machine which it later
wants to invoke, my understanding is that BUILD_CC should be used?
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailm
Yi Zhao (3):
oeqa/runtime/smart: fix hardcoded root directory
oeqa/runtime/logrotate: fix hardcoded root directory
oeqa/runtime/parselogs: escape special character for grep
meta/lib/oeqa/runtime/logrotate.py |8
meta/lib/oeqa/runtime/parselogs.py |6 --
meta/lib/oeqa/r
Sometimes the grep output is not correct if the log message contains
some special characters. Use re.escape to escape all non-alphanumerics
before grep
Signed-off-by: Yi Zhao
---
meta/lib/oeqa/runtime/parselogs.py |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/
Use $HOME instead of /home/root in case user changes the default root
directory by ROOT_HOME
Signed-off-by: Yi Zhao
---
meta/lib/oeqa/runtime/smart.py |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/runtime/smart.py b/meta/lib/oeqa/runtime/smart.py
index
Use $HOME instead of /home/root in case user changes the default root
directory by ROOT_HOME
Signed-off-by: Yi Zhao
---
meta/lib/oeqa/runtime/logrotate.py |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/meta/lib/oeqa/runtime/logrotate.py
b/meta/lib/oeqa/runtime/lo
> On Jan 6, 2016, at 1:22 AM, Ross Burton wrote:
>
> Too many packages haven't been updated to use the new systemd library names,
> so
> enable the compatibility libraries by default.
I think it would be good if we could get them to move. How many such packages
do you see ?
>
> Signed-off-b
On Mon, 2016-01-04 at 11:55 +0100, Patrick Ohly wrote:
> On Mon, 2015-12-28 at 13:00 +, Richard Purdie wrote:
> I think it is indeed a step in the right direction. Having to re
> -create the rootfs directory each time one makes a change to an image
> creation class or image configuration made e
On Wed, 2016-01-06 at 10:30 +1300, Paul Eggleton wrote:
> I like this a lot. I'd idly considered this model before (as I'm sure
> others
> had) as it simplifies a lot of the multi-format image construction
> handling,
> improves incremental performance, and the added granularity makes it
> slight
This patch splits the code in lib/oe/image into separate tasks, one per
image type. This removes the need for the simple task graph code and defers
to the bitbake task management code to handle this instead.
This is a good step forward in splitting up the monolithic code and starting
to make it mo
I've heard complaints from people trying to create more interesting image
types about how hard it is to understand the rootfs/image generation code
and that its a pain to develop/test/debug.
Having looked at it myself, the internal construction of shell functions which
then gets passed into a mult
After the separation of do_rootfs, some rootfs references need changing
to image_complete.
Signed-off-by: Richard Purdie
diff --git a/meta/classes/image-live.bbclass b/meta/classes/image-live.bbclass
index 4a7e2b7..624ff38 100644
--- a/meta/classes/image-live.bbclass
+++ b/meta/classes/image-li
As the next step in splitting up do_image, move the pre and post processing
commands to separate tasks. This also creates the do_image_complete task
which acts as the end marker task for image generation.
Signed-off-by: Richard Purdie
diff --git a/meta/classes/image.bbclass b/meta/classes/image.
Hi Randy,
On Wed, 06 Jan 2016 14:15:49 Randy Witt wrote:
> This is so that the excluded_targets passed to prune_lockedsigs can
> take a partial form such as nativesdk to filter based on partial matches.
>
> Signed-off-by: Randy Witt
> ---
> meta/lib/oe/copy_buildsystem.py | 7 +--
> 1 file
This removes some unneeded items from the extensible sdk to reduce size by
~300MB.
The following changes since commit f8185ff9f8ac697733b41f023cb3a4b98b2f823f:
bitbake: ast: Add filename/lineno to mapped functions (2016-01-06 15:27:35
+)
are available in the git repository at:
git://gi
The nativesdk and crosssdk targets were only getting pulled into the
extensible sdk due to buildtools dependencies being in BB_TASKDEPDATA.
However the nativesdk and crosssdk targets are not needed for the
extensible sdk to be used.
This patch therefore removes them since it reduces the size of th
This is so that the excluded_targets passed to prune_lockedsigs can
take a partial form such as nativesdk to filter based on partial matches.
Signed-off-by: Randy Witt
---
meta/lib/oe/copy_buildsystem.py | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oe/copy_
Hi Alimon
See inline.
Tudor.
On 06/01/2016 18:07, Aníbal Limón wrote:
> Hi again Tudor,
>
> Comments below,
>
> alimon
>
>
>
> On 01/06/2016 09:46 AM, Aníbal Limón wrote:
>> Hi Todor,
>>
>> Comments below, alimon
>>
>>
>> On 01/05/2016 06:13 PM, Tudor Florea wrote:
>>> Hi Anibal, Please se
On 6 January 2016 at 17:31, Lukas Bulwahn
wrote:
> The commit f50e7bc9fed323c5705c0ed992c03e80eeec1dd6 from the
> boostorg/test github repository (branch: develop) [2] addresses
> that issue, but it was not merged in the 1.60.0 release. This
> commit adds this upstream-accepted patch, which was c
On 6 January 2016 at 15:40, Khem Raj wrote:
> fsl ppc build fails are due to glibc or some other reason
>
They're entirely down the their layer (broken fetch, broken recipes).
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openemb
Due to the version update to 1.59.0, the two patches previously
backported in this recipe are now dropped. The actual status of
the arm-intrinsics.patch (reported with Upstream-Status: Backport)
is unknown to the committer, and hence, that patch is kept in the
recipe, even if it is possibly not req
Awais,
this is what I am seeing.
NOTE: Executing RunQueue Tasks
ERROR: Command Error: exit status: 1 Output:
Applying patch 0001-Fix-CVE-2015-8370-Grub2-user-pass-vulnerability.patch
patching file grub-core/lib/crypto.c
Hunk #1 FAILED at 470.
1 out of 1 hunk FAILED -- rejects in file grub-core/l
On Wednesday, January 06, 2016 at 04:41:43 PM, Khem Raj wrote:
> On Wed, Jan 6, 2016 at 3:56 AM, Marek Vasut wrote:
> > On Wednesday, January 06, 2016 at 03:54:11 AM, Khem Raj wrote:
> >> > On Jan 5, 2016, at 6:13 PM, Marek Vasut wrote:
> >> >
> >> > The gcc 5.3 does not build on NIOS2 due to a
Hi,
Highlights include ARM tune rationalisation from LG, no more meta-qt4, moving
from libjpeg to libjpeg-turbo, no more x11vnc.
Ross
The following changes since commit 4bfe2be707bcdbd2379b3fb775d95fcc826307ee:
bitbake: ast: Add filename/lineno to mapped functions (2016-01-05 23:02:52
+)
Hi again Tudor,
Comments below,
alimon
On 01/06/2016 09:46 AM, Aníbal Limón wrote:
> Hi Todor,
>
> Comments below,
> alimon
>
>
> On 01/05/2016 06:13 PM, Tudor Florea wrote:
>> Hi Anibal,
>> Please see my comments inline.
>> Regards,
>> Tudor.
>>
>> On 04/01/2016 20:29, Aníb
If a postinst has a problem (say, qemu crashes) and set -e isn't in operation,
the only mention of the problem is a single line in the rootfs log that doesn't
trigger any warnings.
Signed-off-by: Ross Burton
---
scripts/postinst-intercepts/update_font_cache | 2 ++
scripts/postinst-intercepts/
Hi Todor,
Comments below,
alimon
On 01/05/2016 06:13 PM, Tudor Florea wrote:
> Hi Anibal,
> Please see my comments inline.
> Regards,
> Tudor.
>
> On 04/01/2016 20:29, Aníbal Limón wrote:
>> The whole set is sent to two ML for reviewing purposes the first
>> two patches are for oe-cor
On Wed, Jan 6, 2016 at 3:56 AM, Marek Vasut wrote:
> On Wednesday, January 06, 2016 at 03:54:11 AM, Khem Raj wrote:
>> > On Jan 5, 2016, at 6:13 PM, Marek Vasut wrote:
>> >
>> > The gcc 5.3 does not build on NIOS2 due to a missing MUSL_DYNAMIC_LINKER
>> > definition in it's config file. Add the d
On Wed, Jan 6, 2016 at 2:04 AM, Burton, Ross wrote:
>
> On 6 January 2016 at 03:16, Khem Raj wrote:
>>
>> Same branch now has updated glibc patchset, if you have cycles please try
>> once more.
>
>
> Thanks Khem. When meta-fsl-ppc doesn't cause several failures in every run
> I'll re-fire it so
It would be great if these could be pulled into jethro as well, since
that's where I first noticed that multilib Debian builds were broken.
-Matt
On Wed, Jan 6, 2016 at 4:21 AM, Matt Madison wrote:
> This version adds a fourth patch from Aníbal to skip any
> "unmet dependencies" errors reported
On Wednesday, January 06, 2016 at 03:54:11 AM, Khem Raj wrote:
> > On Jan 5, 2016, at 6:13 PM, Marek Vasut wrote:
> >
> > The gcc 5.3 does not build on NIOS2 due to a missing MUSL_DYNAMIC_LINKER
> > definition in it's config file. Add the definition to fix the build
> > issue. The output produced
* tmp/deploy/deb subdirectories do not get hyphens replaced
with underscores, so don't do that translation when building
the sources list.
* Fix MULTILIB_VARIANTS handling to be more general and
work for all architectures
* Also include a fix for a warning generated by apt
due to missing
From: Aníbal Limón
Rootfs with dpkg was failing due to false-positive in logcheck_error
because current logic of DpkgPM handles missing dependencies failure
using apt-get -f install [1][2].
This support was broken due to addition of logcheck and don't take into
account dpkgpm cases, in order to
Have DPKG_ARCH set by directly invoking a mapping function, rather
than using an anonymous Python function modify the variable under
the hood, so we can have proper handling of overrides.
Also bring in some additional mappings to Debian architecture names
that weren't being handled.
Signed-off-by
This version adds a fourth patch from Aníbal to skip any
"unmet dependencies" errors reported by APT from the initial
install, which were prematurely terminating the rootfs build.
Aníbal Limón (1):
DpkgRootfs: Fix logcheck_error false-positive when use multilib
Matt Madison (3):
package_deb.b
This tells APT that it can use such packages to resolve dependencies
from packages of any architecture in a multilib build.
Signed-off-by: Matt Madison
Signed-off-by: Aníbal Limón
---
meta/classes/package_deb.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/package_deb
On Tue, Jan 5, 2016 at 3:04 PM, Aníbal Limón
wrote:
> Hi,
>
> I fixed the problem and add a 4 patch and sign-off your first tree
> patches also i tested your changes building images in machines: x86-64
> (sato, minimal, multilib), x86(minimal), arm(minimal) and mips(minimal).
> Details below...
>
More PNBLACKLISTs in place, linux-yocto still fails.
== Tested changes (not included in master yet) - bitbake ==
6fd310a world-image: add extra target
== Tested changes (not included in master yet) - openembedded-core ==
4045977 pulseaudio: add PACKAGECONFIG for lirc
6f302fe sstate-sysroot-cruft.
We need to run the clean for all recipes that are being reset before we
start deleting things from the workspace; if we don't, recipes providing
dependencies may be missing when we come to clean a recipe later (since
we don't and couldn't practically reset them in dependency order). This
also impro
We're doing this in a couple of places, let's just find the recipe file
if it exists within the workspace (which it will if it's been added
through "devtool add") when we read in the workspace.
Signed-off-by: Paul Eggleton
---
scripts/devtool | 12 +++-
scripts/lib/devtoo
It's logical that you would want to build BBCLASSEXTENDed items
separately through devtool build, so simply allow that - we're just
passing the name verbatim to bitbake, so all it means is adjusting the
validation.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/__init__.py | 26 +++
Sometimes you need to build a variant of a recipe for the build
host as well as for the target (i.e. BBCLASSEXTEND = "native"); add a
--also-native command line option to "recipetool create" that enables
this and plumb it through from an identical option for "devtool add".
(We could conceivably d
If the recipe file itself was created in the workspace, and it uses
BBCLASSEXTEND (e.g. through devtool add --also-native), then we need to
clean the other variants as well.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/__init__.py | 24
scripts/lib/devtool/standa
* Clone the correct path - we need .git on the end
* Pull from the specified path instead of expecting a remote to be set
* up in the repo already (it isn't by default)
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/sdk.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --g
We read the updateserver setting from the config file but we never
actually used that value - the code then went on to use only the value
supplied on the command line.
Fix courtesy of Dmitry Rozhkov
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/sdk.py | 30 +++---
As a matter of general convention we expect recipe names to be lower
case; in fact some of the packaging backends insist upon it. Since in
this part of the code we're auto-determining the name, we should convert
the name to lowercase if it's not already so that we're following
convention and avoidi
For debugging purposes it's useful to be able to skip the preparation
step so you can inspect what the state of the build system is first.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/sdk.py | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/scripts/l
If the recipe name ends with -native then we should inherit native;
likewise if it starts with nativesdk- then inherit nativesdk.
(Note that the recipe name must actually be specified by the user in
order to trigger this - we won't do it based on any name auto-detected
from e.g. the tarball name.)
A bunch of collected fixes for the extensible SDK, devtool and recipetool.
The following changes since commit 1568f4fa1c8f8abd9b365ecd264841cd4f6b66b1:
bluez5: include the patch only for 5.36 (2015-12-28 13:02:03 +)
are available in the git repository at:
git://git.openembedded.org/ope
Running "raise" with no arguments here is invalid, we're not in
exception handling context. Rather than also adding code to catch the
exception I just moved the check out to the parent function from which
we can just exit.
Signed-off-by: Paul Eggleton
---
scripts/lib/devtool/sdk.py | 13 ++--
The user of the extensible SDK doesn't need to see these.
Signed-off-by: Paul Eggleton
---
meta/classes/populate_sdk_ext.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/populate_sdk_ext.bbclass
b/meta/classes/populate_sdk_ext.bbclass
index be47a77..31704
During extensible SDK installtion, if the build system preparation step
fails we try to put something at the end of the environment setup script
to show an error when it is sourced, in case the user doesn't realise
that the partially-installed SDK is broken. However, an apostrophe in
the message (a
We need to call git update-server-info here on the created repository or
we can't share it over plain http as we need to be able to for the
update process to function as currently implemented.
Signed-off-by: Paul Eggleton
---
scripts/oe-publish-sdk | 4 ++--
1 file changed, 2 insertions(+), 2 de
On 6 January 2016 at 03:16, Khem Raj wrote:
> Same branch now has updated glibc patchset, if you have cycles please try
> once more.
>
Thanks Khem. When meta-fsl-ppc doesn't cause several failures in every run
I'll re-fire it so we can actually get an all-green build!
Ross
--
On 6 January 2016 at 09:42, Belal, Awais wrote:
> Ping2!
>
This is queued for master, will be there shortly.
Ross
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedd
Ping!
BR,
Awais
From: openembedded-core-boun...@lists.openembedded.org
[openembedded-core-boun...@lists.openembedded.org] on behalf of Belal, Awais
Sent: Monday, January 04, 2016 12:53 PM
To: akuster808
Cc: openembedded-core@lists.openembedded.org
Subject
Ping2!
BR,
Awais
From: openembedded-core-boun...@lists.openembedded.org
[openembedded-core-boun...@lists.openembedded.org] on behalf of Belal, Awais
Sent: Thursday, December 31, 2015 6:37 PM
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-co
Too many packages haven't been updated to use the new systemd library names, so
enable the compatibility libraries by default.
Signed-off-by: Ross Burton
---
meta/recipes-core/systemd/systemd_228.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/systemd/sys
Please ignore this one.
I've separated this patch into two and send them to the correct list.
// Qi
On 01/06/2016 04:20 PM, Chen Qi wrote:
The 'stamp-base' related codes are no longer useful, clean them up.
[YOCTO #8468]
Signed-off-by: Chen Qi
---
bitbake/lib/bb/build.py | 4 ++--
bitbak
Remove 'stamp-base' from this file as this flag is no longer used.
[YOCTO #8468]
Signed-off-by: Chen Qi
---
meta/conf/bitbake.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 371af31..51885af 100644
--- a/meta/conf/bi
The 'stamp-base' related codes are no longer useful, clean them up.
[YOCTO #8468]
Signed-off-by: Chen Qi
---
bitbake/lib/bb/build.py | 4 ++--
bitbake/lib/bb/cache.py | 3 ---
meta/conf/bitbake.conf | 2 +-
3 files changed, 3 insertions(+), 6 deletions(-)
diff --git a/bitbake/lib/bb/build.py
62 matches
Mail list logo
