Hello Bruce,
Thank you very much for the quick response. I tried to built in the
kernel changes. But the iptables error persists.
Eventually, I tried to enable systemd again and it still breaks my build
-.-:
test$ bitbake core-image-base
NOTE: Started PRServer with DBfile:
/home/build/test/c
On Fri, Jun 1, 2018 at 11:34 AM, Jon Szymaniak
wrote:
> From my understanding, all that should be required to run the buck-security
> after an image build is adding INHERIT += "check_security" to local.conf. I
> see
> that check_security.bbclass [2] already takes care of appending itself to
> EXT
On 06/01/2018 07:56 PM, Alan Martinovic wrote:
> Yeah, a deep dive it is then. :)
>
> Am just trying to print from the code using the Python debugger (as
> used in the source file).
> self._log.debug("Print this")
>
> but it's not printing anything even when running bitbake with -DDDvvv
wic
As a followup to my question, it might have helped to include some more
details... ^_^;;;
poky.sumo/meta/recipes-devtools/python/python3_3.5.5.bb:do_compile
As near as I can tell, the command below is running the /usr/bin/python
version from my host system, which is 2.7.15rc1, so that might expla
I'm trying to build yocto for two different ARM boards using a rocko and a
sumo distro, but am running into the same problem:
PYTHON_PROJECT_BASE=/home/mclark/Code/Yocto/ODroid/build/tmp/work/aarch64-poky-linux/python3/3.5.5-r1.0/build
\
_PYTHON_HOST_PLATFORM=linux-aarch64 PYTHONPATH=\
/home/mcl
Hello,
I work on the following context :
qt: 5.9.2
SRCREV_qtwebengine = "c11c2c8981e647c1eb2c6753ce77d436b92fff87"
SRCREV_chromium = "cfe8c60903b327ac94406661350f4ac05aa8c21b"
So, I use the layer of QT5 :
https://github.com/meta-qt5/meta-qt5
with the commit : bbb304456978fa9713932e9ff52
I'm working with the rocko branch of the meta-security layer [1], with the
latest poky rocko branch HEAD on an Ubuntu 17.10 machine (technically an
"untested" distro but otherwise fine with Rocko the past).
>From my understanding, all that should be required to run the buck-security
after an image
Here is the idea developed at Atlas Copco.
Not my code, but I thought it useful for this problem
define three bbclasses.
production.bbclass, rnd.bbclass, release.bbclass containing:
==
# Class for use in BBCLASSEXTEND to make it easier to have a single recipe that
# bu
It probably goes to some log file?
Alex
> On 1 Jun 2018, at 14.56, Alan Martinovic wrote:
>
> Yeah, a deep dive it is then. :)
>
> Am just trying to print from the code using the Python debugger (as
> used in the source file).
>self._log.debug("Print this")
>
> but it's not printing anyth
Yeah, a deep dive it is then. :)
Am just trying to print from the code using the Python debugger (as
used in the source file).
self._log.debug("Print this")
but it's not printing anything even when running bitbake with -DDDvvv
On Fri, Jun 1, 2018 at 12:52 PM, Alexander Kanavin
wrote:
> 2018
Thanks a lot everyone, this is very helpful =)
On Fri, Jun 1, 2018 at 2:14 PM, Iván Castell
wrote:
>
>
> 2018-06-01 11:24 GMT+02:00 Alexander Kanavin :
>
>> I have to say defining multiple distros and then tweaking recipes
>> according to those definitions is not a good practice, as recipes shou
2018-06-01 11:24 GMT+02:00 Alexander Kanavin :
> I have to say defining multiple distros and then tweaking recipes
> according to those definitions is not a good practice, as recipes should
> generally only access DISTRO_FEATURES and otherwise be distro-agnostic. The
> above iptables scenario shou
2018-06-01 13:38 GMT+03:00 Alan Martinovic :
> Building them at the same time causes an issue:
>
> Traceback (most recent call lastd):
> File "/home/alan/workspace/senic-os-dev/oe/scripts/lib/wic/filemap.py",
> line 120, in _open_image_file
> self._f_image = open(self._image_path, 'rb')
>
Yes, much better phrasing:
> A single bitbake invocation always builds a single distro for a specific
target machine
Thanks
On Fri, Jun 1, 2018 at 12:18 PM, Alexander Kanavin
wrote:
> If a build is 'a single bitbake invocation', then yes - it builds for a
> single distro and for a specific tar
Hi,
I'm creating two images with the single bitbake command and
on inherits the other (production, and a dev which "require production").
Building them at the same time causes an issue:
Traceback (most recent call lastd):
File "/home/alan/workspace/senic-os-dev/oe/scripts/lib/wic/filemap.py",
l
If a build is 'a single bitbake invocation', then yes - it builds for a
single distro and for a specific target machine, but it can build multiple
recipes (which includes multiple images, as images are defined with
recipes).
Alex
2018-06-01 13:07 GMT+03:00 Alan Martinovic :
> Hey Alexander,
> y
Hey Alexander,
you seem to have a good understanding on the concepts.
Would you say that:
> A build always builds a single distro
is somewhat of a rule?
On Fri, Jun 1, 2018 at 11:24 AM, Alexander Kanavin
wrote:
> I have to say defining multiple distros and then tweaking recipes
> according
Signed-off-by: Dengke Du
---
.../mce-test/files/makefile-remove-ldflags.patch | 23 +++
recipes-kernel/mce-test/mce-test_git.bb| 48 ++
2 files changed, 71 insertions(+)
create mode 100644 recipes-kernel/mce-test/files/makefile-remove-ldflags.patch
crea
I have to say defining multiple distros and then tweaking recipes according
to those definitions is not a good practice, as recipes should generally
only access DISTRO_FEATURES and otherwise be distro-agnostic. The above
iptables scenario should be handled with different image recipes, which
pull i
You are right, my setup is not able to generate two different images at the
same time. To do that, I setup two different builds sharing the download
directory between them.
2018-06-01 11:11 GMT+02:00 Alan Martinovic :
> Thanks for the replay Iván,
> am I reading correctly that this means that you
Thanks for the replay Iván,
am I reading correctly that this means that you create a single image
file per build
(which can be any of the given types)?
You're setup doesn't allow for building the "developent" and
"production" image at the same time?
Be Well,
Alan
On Fri, Jun 1, 2018 at 11:04 AM
I can provide more details. My custom layer has these files related with
distro:
my_layer/conf/distro/include/common.conf
my_layer/conf/distro/develop.conf
my_layer/conf/distro/production.conf
my_layer/conf/distro/integration.conf
As an example of the previous files,
my_layer/conf
2018-06-01 8:46 GMT+03:00 Damien LEFEVRE :
> For the same MACHINE I create the following images:
> - myimage-production
> - myimage-rnd
> - myimage-retail
>
> The production one has production assisted tools for flashing peripheral HW,
> testing vital HW components, writing some serial numbers, etc
Hey,
would really like to see your example.
Am struggling to get creation of these types of images for a while now.
So far have avoided diving into multiple distros because would like to have
the option
of building all the images at the same time (so they are basically the same
distro).
On Fri, J
REGEX, REGEX_URI and GITTAGREGEX are replaced by UPSTREAM_CHECK_REGEX,
UPSTREAM_CHECK_URI and UPSTREAM_CHECK_GITTAGREGEX
Signed-off-by: Yi Zhao
---
rrs/tools/rrs_upstream_history.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rrs/tools/rrs_upstream_history.py
b/rrs/tools
Add logger.setLevel to enable set log level.
Signed-off-by: Yi Zhao
---
rrs/tools/rrs_upstream_email.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/rrs/tools/rrs_upstream_email.py b/rrs/tools/rrs_upstream_email.py
index cdc352d..8ef0b3c 100755
--- a/rrs/tools/rrs_upstream_email.py
+++ b/
26 matches
Mail list logo
