On 03/14/2017 11:12 PM, Robert P. J. Day wrote:
is there, somewhere, a short writeup/summary on this? i can see
emails to this list back in october of last year, just wondering if
there is a wrap-up to this that one can read to pull all the threads
together to understand the consequences.
what shell (or level of POSIX compatibility) does one assume for
writing shell functions in .bbclass files?
i'm looking at kernel-fitimage.bbclass and i see this:
#
# Step 7: Sign the image and add public key to U-Boot dtb
#
if [ "x${UBOOT_SIGN_ENABLE}" = "x1" ] ; then
surely we
sort of related to an earlier question i asked on YP list ... i'm
playing with introducing and generating different KERNEL_IMAGETYPES,
and i want to be able to remove *just* those generated kernel image
types before trying a different variation by setting:
KERNEL_CLASSES
KERNEL_IMAGETYPES
I update my Poky to the latest on master yesterday (i.e., I went from
a version using smart to one using dnf) and when I rebuilt my image I
got the following error:
| cd ${WORKDIR}/build/ext && ${WORKDIR}/recipe-sysroot-native/usr/bin/cmake -E
cmake_link_script
Fixed:
MACHINE = qemuarm64
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "armv7at-neon"
$ bitbake core-image-minimal -cpopulate_sdk
WARNING: gcc multilib setup is not supported for TARGET_ARCH=aarch64
WARNING: gcc multilib setup is
On Monday 13 March 2017 at 13:51:46 +, Mike Crowe wrote:
> On Monday 13 March 2017 at 13:33:27 +, Burton, Ross wrote:
> > On 11 March 2017 at 16:54, Mike Crowe wrote:
> >
> > > ccache apparently does this so that paths in the debug information will
> > > always be
On 14 March 2017 at 17:27, Alexander Kanavin <
alexander.kana...@linux.intel.com> wrote:
> +cls.repo_server.port = 8080
>
What if parallel selftests are running at once? Can this service be
started before the image is created, so the right port can be written into
the image?
Ross
--
When "bitbake -k -S none world" failed, the error printed by
yocto-compat-layer.py contained the stack trace multiple times and did not
contain the stderr output from bitbake, making the error hard to understand
and debug:
INFO:
On 03/15/2017 01:13 PM, Burton, Ross wrote:
+cls.repo_server.port = 8080
What if parallel selftests are running at once? Can this service be
started before the image is created, so the right port can be written
into the image?
I don't know. I only followed what Humberto wrote
As of ccache-3.3, ccache tries to ensure that the paths in the debug
information are always correct. It does this by including the current
directory in the hash if debug output is enabled. It includes support for
detecting remapping via a single -fdebug-prefix-map argument uses the
remapped
On Wed, 15 Mar 2017, Patrick Ohly wrote:
> On Wed, 2017-03-15 at 11:05 +, Burton, Ross wrote:
> > Our shell parser *should* be POSIX compliant. There are a few
> > places where it isn't, but I believe those should be considered
> > bugs. At the end of the day the shell is actually executed
On Wed, 2017-03-15 at 14:39 +0100, Patrick Ohly wrote:
> On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh wrote:
> > Regarding do_rm_work. It should not touch rootfs directories, I believe.
>
> It does, and it should by default because a rootfs can be quite large.
> If it's not going to be reused in
On Wed, 2017-03-15 at 11:05 +, Burton, Ross wrote:
> Our shell parser *should* be POSIX compliant. There are a few places
> where it isn't, but I believe those should be considered bugs. At the
> end of the day the shell is actually executed by /bin/sh or /bin/bash
> anyway, so as long as
On Wed, 2017-03-15 at 13:19 +0200, Alexander Kanavin wrote:
> On 03/15/2017 01:13 PM, Burton, Ross wrote:
> >
> > +cls.repo_server.port = 8080
> >
> >
> > What if parallel selftests are running at once? Can this service be
> > started before the image is created, so the right port can
On Wed, Mar 15, 2017 at 08:24:34AM +0100, Patrick Ohly wrote:
> On Tue, 2017-03-14 at 20:06 +0200, Ed Bartosh wrote:
> > On Tue, Mar 14, 2017 at 06:49:45PM +0100, Patrick Ohly wrote:
> > >
> > > > It's not a big deal to run wic sequentially to produce multiple images,
> > > > but it will create
Building ed into an sstate mirror, then leaving it enabled for
oe-selftest -r signing.Signing.test_signing_sstate_archive results in:
NOTE: recipe ed-1.14.1-r0: task do_populate_lic_setscene: Started
WARNING: ed-1.14.1-r0 do_populate_lic_setscene: Failed to fetch URL
On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh wrote:
> Regarding do_rm_work. It should not touch rootfs directories, I believe.
It does, and it should by default because a rootfs can be quite large.
If it's not going to be reused in another recipe, then it is worthwhile
to remove it.
--
Best
On 15 March 2017 at 10:44, Robert P. J. Day wrote:
> what shell (or level of POSIX compatibility) does one assume for
> writing shell functions in .bbclass files?
>
> i'm looking at kernel-fitimage.bbclass and i see this:
>
> #
> # Step 7: Sign the image and add
On Wed, 2017-03-15 at 16:47 +0200, Ed Bartosh wrote:
> On Wed, Mar 15, 2017 at 04:01:43PM +0200, Ed Bartosh wrote:
> > On Wed, Mar 15, 2017 at 02:41:34PM +0100, Patrick Ohly wrote:
> > > On Wed, 2017-03-15 at 14:39 +0100, Patrick Ohly wrote:
> > > > On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh
On Wed, Mar 15, 2017 at 04:01:43PM +0200, Ed Bartosh wrote:
> On Wed, Mar 15, 2017 at 02:41:34PM +0100, Patrick Ohly wrote:
> > On Wed, 2017-03-15 at 14:39 +0100, Patrick Ohly wrote:
> > > On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh wrote:
> > > > Regarding do_rm_work. It should not touch rootfs
On Wed, 2017-03-15 at 16:01 +0200, Ed Bartosh wrote:
> On Wed, Mar 15, 2017 at 02:41:34PM +0100, Patrick Ohly wrote:
> > On Wed, 2017-03-15 at 14:39 +0100, Patrick Ohly wrote:
> > > On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh wrote:
> > > > Regarding do_rm_work. It should not touch rootfs
On Wed, Mar 15, 2017 at 02:41:34PM +0100, Patrick Ohly wrote:
> On Wed, 2017-03-15 at 14:39 +0100, Patrick Ohly wrote:
> > On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh wrote:
> > > Regarding do_rm_work. It should not touch rootfs directories, I believe.
> >
> It does, and it should by default
sure, no problem
From: Richard Purdie [richard.pur...@linuxfoundation.org]
Sent: Wednesday, March 15, 2017 3:16 PM
To: Bystricky, Juro; openembedded-core@lists.openembedded.org
Cc: jurobystri...@hotmail.com
Subject: Re: [PATCH 1/3] build-appliance-image:
Do not rely on pip3 being installed on the host.
Use pip3-native instead.
[YOCTO#10909]
[YOCTO#11022]
Signed-off-by: Juro Bystricky
---
meta/recipes-core/images/build-appliance-image_15.0.0.bb | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Remove any symlinks before creating new ones to avoid potential build
errors such as:
FileExistsError: [Errno 17] File exists: '../../usr/src/kernel' -> ... '
Signed-off-by: Juro Bystricky
---
meta/recipes-core/images/build-appliance-image_15.0.0.bb | 2 ++
1 file
"pod2man" went missing from BA, but it is required.
This patch fixes the Toaster error:
<...>
ERROR: These tools appear to be unavailable in PATH, please install
them in order to proceed:
pod2man
<...>
[YOCTO#11144]
Signed-off-by: Juro Bystricky
---
The Build Appliance recipe needs several tweaks in order for the BA to build and
to function.
1. Use native pip3: Do not rely on pip3 being installed on host.
This, of course, assumes there is already python-pip3-native support
available.
(a previous patch)
2. Remove symlinks before
On Wed, Mar 15, 2017 at 2:36 AM zhengrq wrote:
> Fixed:
> MACHINE = qemuarm64
> require conf/multilib.conf
> MULTILIBS = "multilib:lib32"
> DEFAULTTUNE_virtclass-multilib-lib32 = "armv7at-neon"
>
> $ bitbake core-image-minimal -cpopulate_sdk
>
>
On Wed, 2017-03-15 at 09:29 +, Peter Kjellerstedt wrote:
> I update my Poky to the latest on master yesterday (i.e., I went
> from
> a version using smart to one using dnf) and when I rebuilt my image
> I
> got the following error:
> [...]
> I.e., it is trying to link a MIPS library with an
On Wed, 2017-03-15 at 15:13 -0700, Juro Bystricky wrote:
> Do not rely on pip3 being installed on the host.
> Use pip3-native instead.
>
> [YOCTO#10909]
> [YOCTO#11022]
>
> Signed-off-by: Juro Bystricky
> ---
> meta/recipes-core/images/build-appliance-image_15.0.0.bb
On Wed, 2017-03-15 at 15:38 +, Ibarra Lopez, Humberto wrote:
> Sorry, missed the previous mail.
>
> I am not sure how to improve the hardcoding there, I don't like it
> either, but couldn't find an alternative. The thing is that we need
> the ip of the host as seen from the target to run
Acked-by: Aníbal Limón
On 03/15/2017 04:01 AM, Patrick Ohly wrote:
> When "bitbake -k -S none world" failed, the error printed by
> yocto-compat-layer.py contained the stack trace multiple times and did not
> contain the stderr output from bitbake, making the error
FWIW, it still doesn't seem to fully work...
I just got this exact error in my morty build. My packageconfigs are:
PACKAGECONFIG="orc yasm"
PACKAGECONFIG_CONFARGS=" --disable-gpl --enable-orc --disable-valgrind
--enable-yasm"
On Thu, Nov 10, 2016 at 03:44:09PM +0100, Martin Jansa wrote:
>
Due to the recently implemented update-alternatives for bash binary,
sanity checker may end up with a (false-positive) error such as:
Error, /bin/sh links to /bin/bash.bash, must be dash or bash
This patch modifies the test: presence of "/bash" or "/dash" in shell binary
name results in pass.
Yeah, it does sound off but we could use it. We could put a mock value in the
ip to the PACKAGE_FEED_URIS var to build this image and once it boths update
that value with the real one. We would have to check that the mock value was
correctly set before updating so we can test the var being
On 03/15/2017 12:39 PM, Juro Bystricky wrote:
Due to the recently implemented update-alternatives for bash binary,
sanity checker may end up with a (false-positive) error such as:
Error, /bin/sh links to /bin/bash.bash, must be dash or bash
This patch modifies the test: presence of "/bash"
On Wed, 2017-03-15 at 11:16 -0700, Joe Slater wrote:
> We want PV values to be easily ordered, so
> use the latest entry in build-compare.changes which
> will also match the date of SRCREV.
>
> Signed-off-by: Joe Slater
> ---
> .../build-compare/build-compare_git.bb
On 15 March 2017 at 12:40, Patrick Ohly wrote:
> Unfortunately bitbake has problems parsing useful things like $( ). Are
> there open bugs about that and/or is it worth filing enhancement
> requests?
>
Absolutely worth filing bugs. Worst case, they get marked as
Sorry, missed the previous mail.
I am not sure how to improve the hardcoding there, I don't like it either, but
couldn't find an alternative. The thing is that we need the ip of the host as
seen from the target to run testimage, but we don’t have the exact value for
that one until qemu is up.
We want PV values to be easily ordered, so
use the latest entry in build-compare.changes which
will also match the date of SRCREV.
Signed-off-by: Joe Slater
---
.../build-compare/build-compare_git.bb |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
Presently, runqemu sets up rootfs as part of network setup.
In case there is no network desired we will end up without rootfs
as well.
This patch sets up network and rootfs independently.
It is also possible to bypass setup of rootfs if QB_ROOTFS is set to "none".
Signed-off-by: Juro Bystricky
Add native pip3 support.
[YOCTO#11049]
[YOCTO#11022]
Signed-off-by: Juro Bystricky
---
meta/recipes-devtools/python/python3-pip_9.0.1.bb | 7 +++
1 file changed, 7 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-pip_9.0.1.bb
Due to the recently implemented update-alternatives for bash binary,
sanity checker may end up with a (false-positive) error such as:
Error, /bin/sh links to /bin/bash.bash, must be dash or bash
This patch modifies the test: presence of "/bash" or "/dash" in shell binary
name results in pass.
Due to the recently implemented update-alternatives for bash binary,
sanity checker may end up with a (false-positive) error such as:
Error, /bin/sh links to /bin/bash.bash, must be dash or bash
This patch is also desired for "morty", even if it may not support
update-alternatives for bash,
On Thu, 09 Mar 2017 18:18:05 +0100
Patrick Ohly wrote:
> On Thu, 2017-03-09 at 17:48 +0100, José Bollo wrote:
> > On Thu, 09 Mar 2017 17:07:54 +0100
> > Patrick Ohly wrote:
> > > Can't you reorder and rebase the patches so that this
> > >
The Eclipse plugin uses cmake from the SDK and currently has issues
because cmake is not installed as a host tool. This patch adds cmake as
a host tool for the sdk/esdk.
This adds ~ 20M to the sdk/esdk which is not alot given the functionality.
-brian
The following changes since commit
The Eclipse plugin uses cmake from the SDK and currently has issues
because cmake is not installed as a host tool. This patch adds cmake as
a host tool for the sdk/esdk.
Signed-off-by: brian avery
---
meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb | 1
On Tue, 2017-03-14 at 20:06 +0200, Ed Bartosh wrote:
> On Tue, Mar 14, 2017 at 06:49:45PM +0100, Patrick Ohly wrote:
> >
> > > It's not a big deal to run wic sequentially to produce multiple images,
> > > but it will create more problems than it solves I believe. It will be
> > > slower and
> >
48 matches
Mail list logo