This converts the two layers to the new override syntax. This was done using
/scripts/contrib/convert-overrides.py
Signed-off-by: Richard Purdie
---
classes/toolchain-scripts-mingw32.bbclass | 8 +++---
conf/machine-sdk/include/mingw32-common.inc | 26 +--
recipes-core
Signed-off-by: Richard Purdie
---
conf/layer.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf/layer.conf b/conf/layer.conf
index 194a55d..5fefa73 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -10,4 +10,4 @@ BBFILE_PRIORITY_meta-mingw = &q
Fix a coupld of mis-converted lines from the automated override
conversion script.
Signed-off-by: Richard Purdie
---
recipes-devtools/gcc/gcc-runtime_%.bbappend | 4 ++--
recipes-graphics/wayland/wayland_%.bbappend | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/recipes
A build flagged for QA (yocto-3.1.10.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.1.10.rc1
Build hash information:
bitbake: 0e0af15b84e07e6763300dcd092b980086b9b9c4
meta-agl: 68c0029602e539d005c33b6c36baa32e34bf67bf
A build flagged for QA (yocto-3.3.2.rc2) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.3.2.rc2
Build hash information:
bitbake: 731fb52eb03338c0bdb2a2256c22c64c22bcbace
meta-agl: ee397d099bf5db91f14f357f874a0fb074208fbe
meta-arm:
To help with the conversion, switch the core configurations to use the new
syntax since this allows testing with the new syntax only.
Signed-off-by: Richard Purdie
---
config.json | 94 ++---
1 file changed, 47 insertions(+), 47 deletions(-)
diff
On Thu, 2021-07-22 at 17:29 -0400, elberger via lists.yoctoproject.org wrote:
> From: Richard Elberger
>
> This patch provides the buildbot system to make the aws-iot-device-sdk-cpp-v2.
> - build on poky
> - meta-openembedded and meta-aws are additional repo dependencies
> - build for the two
On Thu, 2021-07-22 at 16:05 -0400, elberger via lists.yoctoproject.org wrote:
> Hello,
>
> What can I do to move this patch along - or did I miss anything?
> Apologies for my ignorance, it's my first time submitting a patch to YP.
I can't see the patch in the mailing list archives:
A build flagged for QA (yocto-3.4_M2.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.4_M2.rc1
Build hash information:
bitbake: 13e2855bff6a6ead6dbd33c5be4b988aafcd4afa
meta-arm: 9efa3b5683a5dd7ebbf63ff31b889ed589ff7a9a
On Sun, 2021-07-18 at 16:07 -0700, Tim Orling wrote:
> The current code base uses Django 2.2.x which will go out of extended
> support in April 2022, but also holds us back from updating a number of
> dependencies.
>
> Update to the current Django 3.2.5 LTS and also the latest Celery 5.1.2.
>
On Sun, 2021-07-18 at 14:01 +1000, Simon Haines wrote:
> I can't seem to find any information about this error, but I keep getting
> variations of this when building
> hardknott:
>
> Exception: NotADirectoryError: [Errno 20] Not a directory:
> '/home/yocto/rpi64/build/tmp/sysroots-
>
Rather than just ppc/mips, use the pregen-hostkeys on all the qemu targets
since this is using a lot of time on the autobuilders when we don't really
need to. This should avoid some of the testing failures seen on qemuarm
recently.
Signed-off-by: Richard Purdie
---
config.json | 18
On Fri, 2021-07-09 at 14:07 +0530, Milan Shah wrote:
> Well, there was no update on the bug as well as on the patch so I was
> not aware of it.
>
> Thanks, Richard for responding. I'll definitely follow your suggestion
> next time.
We'd normally expect the bug owner to update the status of the
On Fri, 2021-07-09 at 10:51 +0530, Milan Shah wrote:
> Hello All,
>
> My Patch has not been reviewed for the past 7 months. Looking forward
> to see some updates on this.
>
> Please find related links below.
> https://lists.yoctoproject.org/g/yocto/message/51891
>
On Wed, 2021-06-30 at 10:41 +, Cardaillac, Yann wrote:
> Hi Richard,
>
> Many thanks for the fast answer.
>
> > > I’m switching from buildroot to yocto and trying to figure out how to
> > > do the equivalent of a POST_BUILD_SCRIPT.
> > >
> > > Indeed I want to format the images built in a
On Wed, 2021-06-30 at 09:33 +, Cardaillac, Yann wrote:
> I’m switching from buildroot to yocto and trying to figure out how to do the
> equivalent of a
> POST_BUILD_SCRIPT.
>
> Indeed I want to format the images built in a specific format for latter use
> and CI needs.
In OE, the
On Thu, 2021-06-24 at 21:48 -0700, Chuck Wolber wrote:
> All,
>
> Please accept my apologies in advance for the detailed submission. I think
> it is warranted in this case.
>
> There is something... "odd" about the GCC 10 compiler that is delivered with
> Hardknott. I am still chasing it down,
On Thu, 2021-06-24 at 17:40 -0300, Fabio Berton wrote:
> Hi all!
>
> I'm running some test with do_populate_sdk task and I'm seeing this
> on the log:
>
> check_data_file_clashes: Package kmsxx-dbg wants to install file
> /home/builder/build/tmp/work/foo-poky-
>
On Thu, 2021-06-24 at 07:50 -0400, Robert P. J. Day wrote:
> i asked about this once upon a time, so i thought i'd follow up ...
> given the fairly stable state of recent linux distros, is there any
> standard for taking advantage of what *should* be robust native tools
> rather than building
On Wed, 2021-06-16 at 04:43 -0400, sakib.sa...@windriver.com wrote:
> summarize_top_output.py is used to summarize the top
> output that is captured during autobuilder intermittent
> failures.
>
> Use the script to summarize the host top output and
> publish the summary that is created instead of
On Tue, 2021-06-15 at 17:21 +0200, Alexander Kanavin wrote:
> So the memory usage is actually *better* without prelink. And any timing
> benefits are lost in statistical noise, in these tests at least.
The numbers certainly don't look convincing, thanks for running the tests.
> So I do not
On Mon, 2021-06-14 at 20:20 +, Richard Leitner - SKIDATA wrote:
> On Thu, Jun 10, 2021 at 10:57:46AM +0200, Alexander Kanavin wrote:
> > I have the tarball. I think we should toss it somewhere safe and update the
> > recipe, as it is unlikely the old mercurial repo is coming back.
> >
> >
On Fri, 2021-06-11 at 22:30 +0200, Hendrik wrote:
> I was able to reproduce the error even with plain poky (without kas):
>
> ```bash
> git clone -b dunfell https://git.yoctoproject.org/git/poky
> cd poky
> source oe-init-build-env
> bitbake -c populate_sdk_ext core-image-minimal
> ```
>
> After
On Wed, 2021-06-02 at 23:12 -0700, lavkhush2...@gmail.com wrote:
> Hello Guys
> i am building nodejs-12.21.0, facing an issue- ERROR: Nothing PROVIDES
> 'nodejs' nodejs was skipped:
> incompatible with host riscv64-oe-linux (not in COMPATIBLE_HOST)
>
> After modification in .bb file:-
>
On Tue, 2021-05-18 at 07:09 +, Mikko Murto wrote:
> > Lähettäjä: Richard Purdie
> > Lähetetty: tiistai 18. toukokuuta 2021 9.57
> >
> > On Tue, 2021-05-18 at 06:15 +, Mikko Murto wrote:
> > > Hi,
> > >
> > > I've created a ta
On Tue, 2021-05-18 at 06:15 +, Mikko Murto wrote:
> Hi,
>
> I've created a task do_create_spdx that gets some data from packages after
> do_package. The task is currently added with `addtask do_create_spdx after
> do_package before do_packagedata` The data is then enriched and combined in
On Mon, 2021-05-17 at 13:25 +0200, Morten Bruun wrote:
> Hi,
>
> When building on the new hardknott branch I often get the error below, so far
> the solution is to delete the
> tmp directory. Any suggestions?
>
> debug_logfile: fd 2
> pid 6668 [parent 6667], doing new pid setup and server start
On Sat, 2021-05-15 at 22:15 -0400, Brian Hutchinson wrote:
>
>
> On Fri, May 14, 2021 at 12:35 AM Yi Zhao wrote:
> >
> > On 5/14/21 9:40 AM, Brian Hutchinson wrote:
> >
> > > Hi,
> > >
> > > Pretty new to selinux. I've worked through a lot of issues to get this
> > > far but am stumped at
The autobuilders have 128GB memory, we don't want them using 50% which is
the default, 5% should be enough. Also limit the number of threads down
from 48 to something reasonable. This may be partly causing some of our
performance issues?
Signed-off-by: Richard Purdie
---
config.json | 2 ++
1
On Wed, 2021-05-12 at 18:48 +, Kraft, George wrote:
> Could someone point me to a wiki on how yocto testing/QA/conformance is done?
> The Distro Testing Plan wiki seems outdated, and my inquiry to Jose bounced.
The wiki is a bit out of date, sorry. We have been working on
documenting our
On Mon, 2021-05-10 at 21:13 -0700, sateesh m wrote:
> Hi Guys,
>
> I have successfully built core-image-base image using hardknott
> sources. I am trying to build
> sdk & populate_sdk_ext. I have built successfully.but when I running
> ./oecore-x86_64-riscv64-toolchain-ext-
>
On Mon, 2021-05-10 at 13:52 -0700, akuster808 wrote:
>
> On 5/10/21 8:14 AM, Richard Purdie wrote:
> > I appreciate these are difficult times, both for individuals and for
> > businesses. I'd like to conclude by thanking everyone who does participate
> > and contribut
TLDR: The project is seen as mature, employers don't prioritise maintaining
things and we're struggling for maintainers and help with day to day work
Open source projects survive, not just through development work and
contributions of new features but through a whole load of "unglamorous"
day
On Fri, 2021-05-07 at 10:10 +0300, Thomas Hill via lists.yoctoproject.org wrote:
> On Thu, 6 May 2021, 13:44 Martin Jansa wrote:
> > On Thu, May 6, 2021 at 10:57 AM Thomas Hill via lists.yoctoproject.org
> > wrote:
> > > Hi Martin!
>
> > > > On Mon, Nov 16, 2020 at 02:28 PM, Martin Jansa
I'm pleased to be able to announce that the project is planning to have
the April 2022 release next year be our next LTS release.
This fits in with our original announced plan of 2 year cycles and
recognises that the LTS has been well received by members and our
community. It also aligns well
The -j option has the side effect that the output is cached. For a long running
single threaded target, the live output is more useful so switch to it.
Signed-off-by: Richard Purdie
---
config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/config.json b/config.json
On Wed, 2021-05-05 at 00:56 -0700, Chuck Wolber wrote:
> The following code is an effective workaround. It must be added after the
> core-image is inherited.
>
> python () {
> pseudo_ignore_paths = d.getVar('PSEUDO_IGNORE_PATHS')
> result = ','.join([x for x in
On Mon, 2021-05-03 at 11:25 -0700, Sven via lists.yoctoproject.org wrote:
Hi,
I have put together a recipe inheriting from go-mod. This project depends on
> out-of-repo modules that sit in private repos. As long as the SSH key
> required
> to pull the requirements is present as a file (under
On Tue, 2021-05-04 at 18:38 +0200, Alexander Kanavin wrote:
> On Tue, 4 May 2021 at 16:46, Stephen Jolley wrote:
> > We are pleased to announce that our April 2022 release (potentially 3.5)
> > will
> > be the next LTS as per our original two year schedule. If there are
> > features
> >
Add a new target to run layer checks every 24 hours on various layers we don't
test as part of the standard test runs.
Signed-off-by: Richard Purdie
---
config.py | 2 ++
schedulers.py | 5 +
2 files changed, 7 insertions(+)
diff --git a/config.py b/config.py
index 54ec9ce8..82076cd3
btrfs-tools has changed to LGPL-3.1 so to allow util-linux to build,
remove the dependency from its ptest package. This may regress some
ptests but keeps the gplv2 layer working.
Signed-off-by: Richard Purdie
---
conf/distro/include/disable-gplv3.inc | 1 +
1 file changed, 1 insertion(+)
diff
On Sun, 2021-04-18 at 00:17 +0200, Gmane Admin wrote:
> Hi,
> Op 14-04-2021 om 06:59 schreef Richard Purdie:
> > On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote:
> > > On 2021-04-11 12:19 p.m., Alexander Kanavin wrote:
> > > > make already has -l option f
On Fri, 2021-04-16 at 09:28 +0100, Richard Purdie via lists.yoctoproject.org
wrote:
> On Tue, 2021-04-13 at 13:02 -0400, sakib.sa...@windriver.com wrote:
> > add the variables required to collect data to "defaults"
> > so that data is collected on all builds.
> >
On Tue, 2021-04-13 at 13:02 -0400, sakib.sa...@windriver.com wrote:
> add the variables required to collect data to "defaults"
> so that data is collected on all builds.
>
> Signed-off-by: Sakib Sajal
> Signed-off-by: Randy MacLeod
> ---
> config.json | 5 -
> 1 file changed, 4
On Thu, 2021-04-15 at 11:31 -0400, Sakib Sajal wrote:
> On 2021-04-15 9:52 a.m., Richard Purdie wrote:
> > [Please note: This e-mail is from an EXTERNAL e-mail address]
> >
> > On Tue, 2021-04-13 at 13:02 -0400, sakib.sa...@windriver.com wrote:
> > > collect-d
On Tue, 2021-04-13 at 13:02 -0400, sakib.sa...@windriver.com wrote:
> collect-data template can run arbitrary commands/scripts
> on a regular basis and logs the output in a file.
>
> See oe-core for more details:
> edb7098e9e buildstats.bbclass: add functionality to collect build system
>
On Tue, 2021-04-13 at 21:14 -0400, Randy MacLeod wrote:
> On 2021-04-11 12:19 p.m., Alexander Kanavin wrote:
> > make already has -l option for limiting new instances if load average is
> > too high, so it's only natural to add a RAM limiter too.
> >
> > -l [N], --load-average[=N],
On Tue, 2021-04-13 at 14:59 +0100, Richard Purdie via lists.yoctoproject.org
wrote:
> Signed-off-by: Richard Purdie
> ---
> bsp-addition-example.patch | 54 --
> config.py | 3 +++
> 2 files changed, 3 insertions(+
Signed-off-by: Richard Purdie
---
bsp-addition-example.patch | 54 --
config.py | 3 +++
2 files changed, 3 insertions(+), 54 deletions(-)
delete mode 100644 bsp-addition-example.patch
diff --git a/bsp-addition-example.patch b/bsp-addition
Signed-off-by: Richard Purdie
---
config.py | 1 +
schedulers.py | 14 --
2 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/config.py b/config.py
index 299f2aa5..903cb4b8 100644
--- a/config.py
+++ b/config.py
@@ -142,6 +142,7 @@ all_workers = workers
On Fri, 2021-04-02 at 21:44 -0400, Paul Gortmaker wrote:
> [Re: [PATCH RFC 00/21] Git repository sharing for kernel (and other) repos]
> On 02/04/2021 (Fri 23:14) Richard Purdie wrote:
>
> > On Fri, 2021-04-02 at 13:15 -0400, Paul Gortmaker wrote:
&
On Fri, 2021-04-02 at 13:15 -0400, Paul Gortmaker wrote:
> If a clone in the download directory is not static, and was created with
> single-branch to avoid additonal unwanted content, then the fetcher will
> come along and spoil that effort by unconditonally getting refs/* from
> the server and
On Fri, 2021-04-02 at 13:15 -0400, Paul Gortmaker wrote:
> Next Steps:
> ---
> With this being a functional implementation, it seems like a good time to
> get other people looking at it. Ideally step #1 will be getting general
> agreement that this is something we need, something that is
On Fri, 2021-03-26 at 16:04 +0530, Milan Shah wrote:
> It seems like patches sent for error-report-web are not much important to the
> community as this patch has
> not been reviewed/commented on by anyone since 6th January 2021 (more than
> 2.5 months).
>
> Still, I'm sending a reminder one
On Wed, 2021-03-24 at 14:39 -1000, Steve Sakoman wrote:
> From: Richard Purdie
>
> Signed-off-by: Richard Purdie
> (cherry picked from commit 838be1a00c0383b63d1ab60aa991919404b82655)
> Signed-off-by: Steve Sakoman
> ---
> scripts/
On Wed, 2021-03-24 at 14:39 -1000, Steve Sakoman wrote:
> From: Richard Purdie
>
> Signed-off-by: Richard Purdie
> (cherry picked from commit 4b8eab92ee1f68ec8cd680c62e40b17006fa6efc)
> Signed-off-by: Steve Sakoman
> ---
> scripts/generate-tes
On Wed, 2021-03-24 at 14:39 -1000, Steve Sakoman wrote:
> From: Richard Purdie
>
> debian9 has python 3.5 which doesn't work with new qemu versions. Its
> the only remaining 3.5 distro so lets move to a minimum of 3.6.
>
> Signed-off-by: Richard Purdie
> (cher
On Mon, 2021-03-22 at 15:32 +, Richard Purdie via lists.yoctoproject.org
wrote:
> Sorry about the delay on this, we do really need to get this resolved.
> I'm wondering if we should replace the angled brackets test with
> https://github.com/mozilla/bleach which would then remove
Instead of searching for "<", use bleach to sanity input to avoid
any XSS issues.
Signed-off-by: Richard Purdie
---
Post/parser.py | 26 +-
1 file changed, 9 insertions(+), 17 deletions(-)
diff --git a/Post/parser.py b/Post/parser.py
index f411e02..5
On Fri, 2020-02-14 at 10:42 +0800, Changqing Li wrote:
> On 12/11/19 1:45 PM, Changqing Li wrote:
> > On 11/13/19 6:36 PM, Paul Eggleton wrote:
> > > Hi Changqing,
> > >
> > > Some comments below.
> > >
> > > On Tuesday, 12 November 2019 9:32:53 PM NZDT
> > > changqing...@windriver.com wrote:
>
On Mon, 2021-03-15 at 17:01 +0100, Zoran wrote:
> > How can I instruct Yocto to execute do_image_cpio first?
>
> YOCTO people are entitled to answer that question. Aren't ya, INTEL folks???
>
> Actually, iNTEL (IOTG) is responsible for that (since YOCTO support is
> 90% from INTEL), and I assume
On Tue, 2021-03-02 at 20:42 +, Diego Santa Cruz via lists.yoctoproject.org
wrote:
> > -Original Message-
> > From: yocto@lists.yoctoproject.org On
> > Behalf Of Steve Sakoman via lists.yoctoproject.org
> > Sent: 02 March 2021 21:06
> > To: Steve Sakoman
> > Cc:
On Fri, 2021-02-26 at 14:18 +, Mikko Murto wrote:
> Hello,
>
> I'm developing a meta layer to save details about an image created by Yocto
> to an
> SPDX document ( https://github.com/doubleopen-project/meta-doubleopen).
>
> I've encountered two issues regarding package names in
On Fri, 2021-02-19 at 10:18 -0500, Randy MacLeod wrote:
> On 2021-02-19 1:44 a.m., Chen Qi wrote:
> > Hi Anibal,
> >
> > The ptest-runner repo seems to be messed up.
> > This patch is no longer there, yet the SRCREV in ptest-runner recipe
> > refers to this commit.
> >
> > $ git show
This code wants to disable GPLv3 and GPLv3+ however the pattern
didnt specify that and with recent changes in OE-Core, it needs
to be specific. Update the pattern to be specific.
Signed-off-by: Richard Purdie
---
conf/distro/include/disable-gplv3.inc | 2 +-
1 file changed, 1 insertion(+), 1
On Thu, 2021-02-18 at 14:58 +0100, Yann Dirson wrote:
>
>
> Le mar. 16 févr. 2021 à 18:43, Pokybuild User
> a écrit :
> >
> > Build hash information:
> >
> > bitbake: 0a3bf681530bd63fc0036ca81ef868ab53fde56c
> > meta-arm: aa63e31b6edb5197764c21434219050ab51f0fbd
> > meta-gplv2:
On Tue, 2021-02-16 at 11:43 -0800, rustyhow...@gmail.com wrote:
> "time bitbake recipe" is perfect for manual things. But I wanted to
> also measure the recipe times when building the entire image. I
> ended up creating a bbappend with new pre/post tasks for the main
> tasks (fetch, unpack,
On Tue, 2021-02-02 at 11:54 +0100, Meh Mbeh Ida Delphine wrote:
> From: Meh Mbeh Ida Delphine
>
> Added SPDX headers in all source files except src/makecrc.c since it is not
> copyrighted.
> Skipped Makefile.am as well.
> Also cleared redundant license text.
> Updated README file with correct
On Mon, 2021-02-01 at 15:40 +0100, Martin Jansa wrote:
> can I get the write access to meta-python2 as mentioned above?
>
> I have 2 fixes to make it parse able with latest oe-core:
> https://lists.openembedded.org/g/openembedded-devel/message/89201
>
On Wed, 2021-01-27 at 09:45 +, Jose Quaresma wrote:
> Hi All,
> gstreamer1.0: fix failing ptest
> https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7b90027aac9fa41b3dc98765151d761df8dabb97
>
> Is this commit present yocto-3.3_M2.rc1 ?
Just to confirm, it wasn't so this should be
On Fri, 2021-01-29 at 13:48 -0600, Andrew Geissler wrote:
>
> > On Jan 29, 2021, at 10:54 AM, Richard Purdie
> > wrote:
> >
> > On Fri, 2021-01-29 at 08:40 -0800, Andrew Geissler wrote:
> > > > What was SDKMACHINE set to before?
> > >
On Fri, 2021-01-29 at 08:40 -0800, Andrew Geissler wrote:
> > What was SDKMACHINE set to before?
>
> Hey Richard, thanks for the quick response.
>
> We did not have it set. It looks like this recent commit is what
> changed things on us:
>
> commit c74ec1dd7393b9dc7bec1a3ca2ed0a56fb18d8fb
>
On Fri, 2021-01-29 at 06:38 -0800, Andrew Geissler wrote:
> Over in OpenBMC, we utilize a mix of x86 and ppc64le machines for our
> CI.
>
> Our latest rebase of poky master
> (https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/39533/) has
> started failing to compile on our ppc64le machines
On Thu, 2021-01-28 at 16:18 +0100, Marek Belisko wrote:
> Hi,
>
> I have repo where I'm using lfs. I've added to my SRC_URI =
> "git://.. ;lfs=1" and the project is fetched but the issue is that
> lfs files are shown as references only (content is not fetched).
> I briefly checked git fetcher
Signed-off-by: Richard Purdie
---
README | 6 ++
1 file changed, 6 insertions(+)
diff --git a/README b/README
index c17f74a..af3ace9 100644
--- a/README
+++ b/README
@@ -15,3 +15,9 @@ Layer Maintainer: Joshua Watt
Please send changes to the yocto mailing list with [meta-mingw
Signed-off-by: Richard Purdie
---
.../libiconv/libiconv/autoconf270.patch | 17 +
recipes-support/libiconv/libiconv_1.15.bb | 3 ++-
2 files changed, 19 insertions(+), 1 deletion(-)
create mode 100644 recipes-support/libiconv/libiconv/autoconf270.patch
diff --git
Signed-off-by: Richard Purdie
---
.../grep/grep-2.5.1a/autoconf270.patch| 27 +++
recipes-extended/grep/grep_2.5.1a.bb | 1 +
2 files changed, 28 insertions(+)
create mode 100644 recipes-extended/grep/grep-2.5.1a/autoconf270.patch
diff --git a/recipes-extended
Signed-off-by: Richard Purdie
---
.../diffutils/diffutils-2.8.1/autoconf270.patch | 17 +
recipes-extended/diffutils/diffutils_2.8.1.bb | 1 +
2 files changed, 18 insertions(+)
create mode 100644 recipes-extended/diffutils/diffutils-2.8.1/autoconf270.patch
diff --git
Signed-off-by: Richard Purdie
---
.../bash/bash-3.2.57/autoconf270.patch | 17 +
recipes-extended/bash/bash_3.2.57.bb| 1 +
2 files changed, 18 insertions(+)
create mode 100644 recipes-extended/bash/bash-3.2.57/autoconf270.patch
diff --git a/recipes
On Thu, 2021-01-28 at 18:53 +0100, Ayoub Zaki via
lists.yoctoproject.org wrote:
> Hello I created a new task that I want to run for every recipe of my
> image but only for target recipes and skip all native, sdk,...
> mytask.bbclass:
>
> addtask do_mytask after do_install
>
> do_mytask() {
>
On Wed, 2021-01-27 at 10:32 -0800, chuck kamas via
lists.yoctoproject.org wrote:
>
> As part of our image we build our company's application. This
> application becomes part of the image and is executed when the image boots.
>
> My question is how to have the binary image also be available
On Tue, 2021-01-26 at 09:00 -0800, Rudolf J Streif wrote:
> I have been scratching my head over building openjdk-8 with multilib for
> an aarch64 system. Essentially, I want to use 32-bit OpenJDK on the
> 64-bit system.
>
> Theoretically adding to local.conf
>
> require conf/multilib.conf
>
On Tue, 2021-01-19 at 20:22 +, Monsees, Steven C (US) wrote:
> All but the following downloaded except these which failed (timing out):
>
> https://sourceware.org/elfutils/ftp/0.177/elfutils-0.177.tar.bz2
> https://download.qemu.org/qemu-4.1.0.tar.xz
>
On Tue, 2021-01-19 at 14:08 +, Monsees, Steven C (US) wrote:
> That was set : export BB_GENERATE_MIRROR_TARBALLS=1
Just to be clear, where did you set that? In a .conf file? If so, you
don't need the export bit. If it was in a shell it probably wouldn't
work.
Also, you didn't answer my other
On Tue, 2021-01-19 at 13:42 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
> When I generate MIRROR TARBALLS for my build it does not appear to
> generate all the required tarballs…
>
> I tested by tested by rebuilding with “BB_NO_NETWORK = 1”, and
> received the following build
On Sat, 2021-01-16 at 16:48 +0200, Daniela-Marinela Bistrean wrote:
> Hello again,
> I solved the mystery and I am describing it here in case anyone has
> the same problem.
>
> Basically, what I omitted last time and seems to be critical to the
> problem is that I was running a virtual machine.
On Mon, 2021-01-04 at 11:44 +0100, Konrad Weihmann wrote:
> I have a bunch of custom testcases (oeqa/runtime/cases) which are
> interacting with "d" from the build host - basically fetching some
> info
> while executing the test, e.g.
>
> foo = self.tc.td['MY_CUSTOM_VAR']
>
> What I've seen is
On Sun, 2021-01-03 at 10:44 -0800, Paul D. DeRocco wrote:
I've been resurrecting an old Pyro project under Gatesgarth. It's an
Intel
32-bit system that needs maximum speed, so I decided to try to build
the
system and application as 64-bit, for more registers. It pretty much
worked
on the first
On Fri, 2020-12-18 at 16:51 -0500, Jérôme Carretero wrote:
> On Fri, 18 Dec 2020 20:34:01 +
> "Richard Purdie" wrote:
>
> > The challenge is that Yocto Project lets you build your own custom
> > software, which means you also end up in your own BoM situat
Hi,
On Fri, 2020-12-18 at 15:15 -0500, Jérôme Carretero wrote:
> Please correct me if I'm wrong but as far as I understand it, as of
> today the flow for generating SPDX data to build software BoMs,
> documented eg. in:
>
> - https://www.fossology.org/get-started/basic-workflow/
> -
>
On Mon, 2020-12-07 at 16:15 +, Pokybuild User wrote:
> A build flagged for QA (yocto-3.2.1.rc1) was completed on the
> autobuilder and is available at:
>
>
> https://autobuilder.yocto.io/pub/releases/yocto-3.2.1.rc1
>
>
> Build hash information:
>
> bitbake:
On Thu, 2020-11-26 at 14:44 +, Valek, Andrej wrote:
> No it's not a leftover. I've just copied it from kernel.bbclass,
> where this task is written correctly. But you can change it to
> previous version I guess.
I'm trying to work out why we need the extra dependencies when the
tasks are
On Wed, 2020-11-25 at 18:20 +0100, Andrej Valek wrote:
> - correctly save files into sstate
> - fix: ERROR: Task linux-dummy.do_fetch attempted to execute
> unexpectedly
>
> Signed-off-by: Andrej Valek
> ---
> meta/recipes-kernel/linux/linux-dummy.bb | 6 --
> 1 file changed, 4
On Sun, 2020-11-22 at 19:16 -0700, Michael Callahan wrote:
> I am having trouble with sstate caching of my os-release.bbappend and
> am stuck. The simple example file looks like something below, where
> I
> am setting a variable from a computed python function. What's the
> magic
> to make the
On Thu, 2020-11-12 at 15:43 -0800, Jate Sujjavanich wrote:
> I have sussed out several behaviors of the image build having to do
> with reproducible builds. It seems like bitbake creates the rpm with
> the correct modification times per the reproducible_builds bbclass.
> When do_rootfs installs
On Mon, 2020-11-09 at 09:14 +, Ross Burton wrote:
> DEPEND on python3 and python3-native then.
Note that whilst the python headers and library will be in recipe-
sysroot, the python3 binaries will not. This is because they're
designed to run on the target, not the host you're building on so
On Thu, 2020-10-01 at 11:59 +0530, Aashik Aswin wrote:
> Hi Developers,
>
> I recently migrated my machine to Red Hat 8 , I am using Yocto Thud
> to build my customized yocto image.
> However, I am seeing the following Build Issue while compiling Perl-
> native
>
> /usr/include/errno.h:48:10:
On Mon, 2020-09-28 at 10:34 +0200, Robert wrote:
> I tried the latest uninative from the same link, it will remove the
> warning but it doesn't solve the problem.
> If something else is wrong/different I would very much like a
> suggestion where to start looking for this difference.
> Finding
On Fri, 2020-09-25 at 14:47 -0400, Randy MacLeod wrote:
> pseduo patches are usually sent to the yocto list so
> I've added that list and only BCCed oe-core here so
> people know where to look for follow-up.
In Sakib's defence, did you read the README in pseudo? :)
"Discussions and patches
[the original email bounced for some reason, resending to the list]
A build flagged for QA (yocto-3.1.3.rc1) was completed on the
autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.1.3.rc1
Build hash information:
bitbake:
401 - 500 of 709 matches
Mail list logo
