Is your layer present in build/conf/bblayers.conf ?
On 06/03/18 14:07, Vincent Daanen wrote:
Dears,
I want to build an image using systemd and system-networkd as network
manager and set static ip address to eth0.
To do so, I use a bbappend file to systemd.
The problem is that the systemd_%
Hi
I'm having some trouble using dm-verity for a squashfs root file system
that seems to be related to the
Atmel SHA hw accelerator in the kernel, CONFIG_CRYPTO_DEV_ATMEL_SHA
Some info about my setup:
* I'm using a board with a SAMA5D4 CPU.
* I'm using Yocto rocko for building an image for tha
Hi
Short story: I'm using rocko and have a recipe for Linux kernel 4.14.14
based on linux-yocto.inc, some kernel fragments end up in the resulting
.config, other don't, if regenerate fragments using menuconfig +
diffconfig seems ok.
Long story:
In my recipe linux-stable_4.14.bb I have an inc
poky-linux-gnueabi/component/1.0/recipe-sysroot-native
Also all the dependencies are there.
Cheers.
On 01/02/18 13:39, Mircea Gliga wrote:
I have a problem starting from the rocko upgrade and related to the
Recipe-specific Sysroots introduced in Yocto 2.3
Our project uses cmake. So out recipe ha
Hi
> I am not sure it makes sense to build and add both the static and
dynamic libs to an SDK.
The idea is that I want everything that is needed to build the app in
the SDK and I don't want to individually specify what goes in because
it's error prone and you can forget something.
Some pkgs
-version.cmake
│ ├── fmt-targets.cmake
│ └── fmt-targets-release.cmake
├── fmt-doc
├── fmt-locale
└── fmt-staticdev
└── usr
└── lib
└── libfmt.a
See my notes below:
On 07/02/18 14:12, Robert Berger wrote:
Hi,
On 2018-02-07 09:46, Mircea Gliga
On 2018-02-06 14:53, Mircea Gliga wrote:
Hello,
I have a problem providing a static library in the SDK:
I have a recipe that builds a library. It outputs an -dev pkg with
the /usr/{include,lib} libs in it and a -staticdev pkg with the
static library.
The main pkg is empty, in my recipe I hav
Hello,
I have a problem providing a static library in the SDK:
I have a recipe that builds a library. It outputs an -dev pkg with the
/usr/{include,lib} libs in it and a -staticdev pkg with the static library.
The main pkg is empty, in my recipe I have added ALLOW_EMPTY_${PN} = "1"
because the
I have a problem starting from the rocko upgrade and related to the
Recipe-specific Sysroots introduced in Yocto 2.3
Our project uses cmake. So out recipe has:
DEPENDS = "cmake-native [...]"
So cmake ends up in
build/tmp/work/cortexa5hf-neon-poky-linux-gnueabi/component/1.0-r0/recipe-sysroot-n
Hi guys
>libgcc.a is "out-f-the-box" in rocko 25MB, but why should it be
integrated in rootfs ?
I asked myself the same question. Not clear for me yet how and why it
gets in the rootfs.
Thanks and regards
Mircea
On 11/01/18 13:51, Stefano Babic wrote:
Hi Zoran, Mircea,
On 11/01/2018 11:
Hello
I just upgraded from krogoth to rocko, and noticed the resulting rootfs
image increased significantly.
What stands out is a big bump in size for
/usr/lib/arm-poky-linux-gnueabi/7.2.0/libgcc.a from 5 MB in krogoth(gcc
5.3.0) to 25 MB in rocko.
Can someone shed some light ? What can be do
Let's put it the other way around. Does anyone know a recipe that uses
an shell script to build something (which must set the environment
correctly and call make itself) ?
Any hints are appreciated.
Thanks
Mircea
On 20/12/17 11:37, Mircea Gliga wrote:
I'm trying to figure the
mv u-boot${DTB}.bin
${3}/binaries/${MACHINE}-u-boot-${BINARY_TYPE}${DTB}.bin
}
buildConfiguration first_defconfig "debug" "first" "-dtb" "prod_keys"
buildConfiguration second_defconfig "loader" "first" "-dtb" ""
bu
Hello
I have a build.sh script used to build outside yocto, after sourcing the
build environment.
I want to use the same build.sh script inside the recipe, in the
do_compile task, something like:
do_compile () {
./build.sh ${MACHINE}
}
The build.sh script eventually calls make for several
Hi list
See below
On 11/12/17 15:22, Mircea Gliga wrote:
On 11/12/17 15:06, Paul Barker wrote:
On Mon, Dec 11, 2017 at 12:43 PM, Mircea Gliga
wrote:
So I went further and I tested in a VM running Debian 9 - there it
works:
It looks like I get a Permission denied while building rocko only
On 11/12/17 15:06, Paul Barker wrote:
On Mon, Dec 11, 2017 at 12:43 PM, Mircea Gliga wrote:
So I went further and I tested in a VM running Debian 9 - there it works:
It looks like I get a Permission denied while building rocko only on Debian
8, *not* on Debian 9.
Debian 8 is listed as
he problem.
Thanks
On 11/12/17 09:58, Mircea Gliga wrote:
Hello,
I have a working krogoth build - I build images etc, everything is fine.
Then I wanted to try a rocko build, I installed the needed host
packages:
http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#pack
I installed autoconf and automake, result is the same. bitbake still
tries to fetch the respective packages, it doesn't use the ones provided
by the system, and that makes sense... It creates its own toolchain.
As I understand the *Permission denied* error pops up during do_fetch,
when it trie
ur problem. Lets hope.
Zoran
On Mon, Dec 11, 2017 at 8:58 AM, Mircea Gliga
mailto:mircea.gl...@vitheia.com>> wrote:
Hello,
I have a working krogoth build - I build images etc, everything is
fine.
Then I wanted to try a rocko build, I installed the needed h
Hello,
I have a working krogoth build - I build images etc, everything is fine.
Then I wanted to try a rocko build, I installed the needed host
packages:
http://www.yoctoproject.org/docs/2.4/yocto-project-qs/yocto-project-qs.html#packages
Then sourced env and /bitbake core-image-minimal/.
So n
ed ncurses inside
YOCTO (in Open Embedded/meta layer, my best guess).
Zoran
On Wed, Dec 6, 2017 at 7:31 AM, Mircea Gliga <mailto:mircea.gl...@vitheia.com>> wrote:
Hello
We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb
<http://linux-stable_4.8.bb
Hello
We are using in our layer a kernel 4.8 recipe (linux-stable_4.8.bb)-
everything ok.
I'm trying to upgrade to 4.14, I created a new recipe
linux-stable_4.14.bb. They live side by side, for now.
But with the 4.14 kernel when running `bitbake -c menuconfig
linux-stable`, the new terminal co
Hi
I think there is a problem in the dnsmasq init script related to the pidfile
|
test -z"${PIDFILE}" && PIFILE="/run/dnsmasq.pid"
|
The script defines a variable PIFILE, notice the missing "D" from PID.
And then it doesn't use that variable anymore.
It only uses the PIDFILE one.
So, if yo
In my layer I've defined a separate image for development and a separate
one for production, eg myimage-dbg.bb and myimage.bb
The difference between them is that the devel one has extra packages
installed.
So, if you want to build a development image you build the `myimage-dbg`
image, else the o
org/docs/latest/mega-manual/mega-manual.html#var-DEPLOY_DIR_IMAGE>
afterwards."
So I should just replace ${DEPLOY_DIR_IMAGE} with ${DEPLOYDIR} and I get
the same behaviour as before + the benefit of sstate cache ?
Thanks
On 09/03/17 09:22, Patrick Ohly wrote:
On Thu, 2017-03-09 at 08:
Long story short: I have problems building an image, in a clean build
directory, reusing the shared state cache and downloads from a previous
build.
A file created in the do_deploy_append task is not created(restored)
anymore when building using a previous sstate.
And now the long description:
Hi
I'm using yocto-autobuilder to build my images. I have a GitPoller
scheduler, that triggers a build when one of the layers, eg
meta-mylayer, changes.
In my buildset I have something like:
[...]
repos: [{'poky':
{'repourl':'git://git.yoctoproject.org/poky',
'layerve
Does anyone has this issue also ?
Any input ?
Thanks
On 28/10/16 15:36, Valentina Skorpion wrote:
Hello everyone,
I have been using yocto jethro in order to build my custom Linux
distribution for several devices ( qemuarm , sama5d4, etc) . I have
used the linux-yocto 4.1.5 kernel
According to the docs here
http://www.yoctoproject.org/docs/2.1.1/mega-manual/mega-manual.html#structure-your-layers
one can specify variables that are machine specific, eg
KERNEL_DEVICETREE_qemuarm = "versatile-pb.dtb". I can't find a reference
on how to create a task specific only for a certa
Thanks Bruce for your help!
It works now, with the defconfig from 4.8.
Have a nice day !
Mircea
On 09/02/2016 06:26 PM, Bruce Ashfield wrote:
On 2016-09-02 09:58 AM, Bruce Ashfield wrote:
On 2016-09-02 03:51 AM, Mircea Gliga wrote:
Hi Bruce,
Do you have any new input in regards with
Hi Bruce,
Do you have any new input in regards with qemuarm booting with kernel
4.7.2 LTS ?
Have you managed to test this ?
I wander if this can be reproduce elsewhere and what's the solution for it.
Thanks
Mircea
On 08/30/2016 06:09 PM, Bruce Ashfield wrote:
I'm finishing up 4.8 today, but
9/2016 04:02 PM, Bruce Ashfield wrote:
On 2016-08-29 07:34 AM, Mircea Gliga wrote:
Hi
I'm using krogoth and trying to create a qemu arm machine with the
latest stable kernel 4.7.2.
I created a recipe,recipes-kernel/linux/linux-stable_4.7.bb, in my layer
with the following contents:
Hi
I'm using krogoth and trying to create a qemu arm machine with the
latest stable kernel 4.7.2.
I created a recipe,recipes-kernel/linux/linux-stable_4.7.bb, in my layer
with the following contents:
---
inherit kernel
require recipes-kernel/linux/linux-yocto.inc
FILESEXTRAPATHS_prepend := "
ta-networking
meta-python
meta-ruby
meta-multimedia = "jethro:d69386740b85b7865ea1ca844b91bbacd27041d8"
Have a nice day.
On 07/26/2016 06:31 PM, Bruce Ashfield wrote:
On 2016-07-26 02:32 AM, Mircea Gliga wrote:
Hello
I have my own layer and I am trying to configure the kernel usin
Hello
I have my own layer and I am trying to configure the kernel using
partial configs.
I'm trying to enable netfilter support into the kernel - not as modules,
so I set the CONFIG to "y"
I've created a bbappend file in my layer, here:
recipes-kernel/linux/linux-yocto_3.14.bbappend
The c
Hello
I have my own layer and I am trying to configure the kernel using
partial configs.
I'm trying to enable netfilter support into the kernel - not as modules,
so I set the CONFIG to "y"
I've created a bbappend file in my layer, here:
recipes-kernel/linux/linux-yocto_3.14.bbappend
The c
Hi
This part of the documentation is of interest:
http://www.yoctoproject.org/docs/2.0.2/dev-manual/dev-manual.html#configuring-the-kernel
The idea is that the .config file is located in your Build Directory, in
the area where the specific kernel is built. Could be something like this:
poky/b
37 matches
Mail list logo
