Hi Richard,
On 2022-09-21 00:11, Richard Purdie wrote:
On Tue, 2022-09-20 at 23:05 +0200, Peter Bergin wrote:
Hi,
I'm working on a recipe for libtraceevent
(https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git) that is
needed for newer trace-cmd. I'm confused about an e
N} += "${libdir}/traceevent/plugins"
$ cat
../../sources/meta-openembedded/meta-oe/recipes-kernel/trace-cmd/files/0001-libtraceevent-make-it-possible-to-set-libdir-and-man.patch
From 2014d037d3488f1a53e1c0c83263e77322ac14ef Mon Sep 17 00:00:00 2001
From: Peter Bergin
Date: Mon, 19 Sep 2
On 2022-06-28 17:54, Randy MacLeod wrote:
On 2022-06-28 07:38, Richard Purdie wrote:
On Tue, 2022-06-28 at 11:00 +0200, Peter Bergin wrote:
When building rust-cross-canadian-aarch64 the file
'tmp/work/x86_64-nativesdk-pokysdk-linux/rust-cross-canadian-aarch64/1.60.0-r0/targets/aarch64
On 2022-06-28 12:09, Richard Purdie wrote:
On Tue, 2022-06-28 at 11:00 +0200, Peter Bergin wrote:
On 2022-06-19 22:47, Peter Bergin wrote:
The reason for this issue seems to be this commit:
commit 781eaa955dce5deab47371c25dae72b36c011900
Author: Richard Purdie
Date: Sat
Hi again,
some progress on this issue.
On 2022-06-19 22:47, Peter Bergin wrote:
Hi,
I experience build failure in the compilation step of the recipe
rust-cross-canadian-aarch64. I've used latest master from poky and
just changed the MACHINE to qemuarm64. When I execute 'bitbake
Hi,
I experience build failure in the compilation step of the recipe
rust-cross-canadian-aarch64. I've used latest master from poky and just
changed the MACHINE to qemuarm64. When I execute 'bitbake
rust-cross-canadian-aarch64' it ends up in an error with object files in
wrong format. I have
On 2022-01-20 07:05, mihirdav...@gmail.com wrote:
*recently tried to add ALSA support to core-image-minimal . by adding
following lines into local.conf: MACHINE_FEATURES+="alsa"
DISTRO_FEATURES+="alsa" CORE_IMAGE_EXTRA_INSTALL+="alsa-utils" but got
error of which I have attached image. *
plea
Hi,
On 2022-01-19 13:16, Michael Opdenacker wrote:
Greetings,
I reused a simple "hello" recipe and added a non-matching checksum to it:
...
SRC_URI = "file://helloworld.c"
SRC_URI[md5sum] = "34f0efd76b4f188833cdd129"
...
The rest of the recipe comes from
https://git.openembedded.org/o
On 2021-11-10 21:44, chiefsleepy...@gmail.com wrote:
I have a weird thing going on with *__DATE__* and *__TIME__* when
building my app in the yocto environment. I'm building for
"genericx86-64" and I'm using __DATE__ and __TIME__ in my source to
show what the build date/time of my app is at ru
Hi Matthias,
On 2021-09-01 17:11, Matthias Klein wrote:
Hello Peter,
I'm not sure it's that simple.
Sorry for my quick and a bit oversimplified response. I did my first
build on an older version (3.20) where ubxtool was not built but present
in the repo root. I see now that in 3.23 gpsd have
Hi Matthias,
On 2021-09-01 12:33, Matthias Klein wrote:
Hello,
is it somehow possible to add the ubxtool in the gpsd-utils package?
(I use the current master branch)
gpsd recipe is located in meta-oe. As the ubxtool file is present in the
build it is possible to add it. Just make sure it is
Hi Matthias,
On 2021-08-31 09:03, Matthias Klein wrote:
But I have not found a way to set the password with EXTRA_USERS_PARAMS.
Do you know a working variant?
Is it a requirement that you need to regenerate the hash on every build?
If not one solution can be:
inherit extrausers
#
On 2021-08-30 14:54, Matthias Klein wrote:
Hello,
I am trying to find a working alternative for the old -P option.
Previous:
EXTRA_USERS_PARAMS = "usermod -P toor root;"
The suggestions from this thread don't seem to work:
https://lists.openembedded.org/g/openembedded-core/topic/84548199
Cu
Hi,
On 2021-02-22 14:29, Mauro Ziliani wrote:
Hi all
Is it possible to include a fine in local.conf?
yes. Just add "include my.conf" in your configuration.
https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-metadata.html#include-directive
Regards,
/Peter
MZ
On 2019-12-03 16:28, Bruce Ashfield wrote:
I'm assuming that you mean those headers are in a separate package and
are installed into the dependent packages sysroot (or the SDK in your
descriptin) via other means that linux-libc-headers .. if so, yes,
that is the right thing to do.
Thanks Bruce!
On 2019-12-02 14:44, Bruce Ashfield wrote:
On Mon, Dec 2, 2019 at 4:14 AM Mike Looijmans wrote:
On 01-12-19 22:57, Peter Bergin via Lists.Yoctoproject.Org wrote:
Hi,
I'm currently working in a project using Yocto 2.6 (thud) release. It has
default kernel v4.18 and also linux-libc-he
Hi,
I'm currently working in a project using Yocto 2.6 (thud) release. It
has default kernel v4.18 and also linux-libc-headers from kernel v4.18.
In my project we will use kernel v4.1. I would like advice how to handle
the linux-libc-headers package for my project, should I use the v4.18
head
17 matches
Mail list logo
