Hi,
I am looking to use gcc built by yocto sdk with –m32 option.
I changed MACHINE to genericx86-64 local.conf and also added these lines to be
able to add multilib support with gcc.
IMAGE_INSTALL_append = " glibc-staticdev"
NO32LIBS = "0"
require conf/multilib.conf
MULTILIBS =
Hi Chen Qi
We got some help from the Yocto team and this seems to be a known issue.
Basically the recipe had these two lines below
SRCREV = "${AUTOREV}"
PV = "master+git${SRCPV}"
These lines force the eSDK to pull the latest code if there is a change in
the revision in the upstream git repo.
I usually build using bitbake -c populate_ext_sdk core-image-minimal
This builds the SDK in tmp/deploy/sdk in the form of a shell script
(which is actually a tar file with a script wrapper as a preamble).
running the script installs the sdk (interactively). Hope this helps.
Thanks
Sunil Mukundan
I want to run latest java (version 162b12) which is given in latest
meta-java branch (sumo) for the colibri-imx6 module(armv7 architecture)
from Toradex.
Currently I'm using latest poky version Sumo, and all the latest branch
for different layers.
I'm able to compile latest java
I am trying to build core-image-minimal for qemu86, I am always getting the
following error.
I have seen this message with sumo branch also, but there it was coming as
warning.
ERROR: core-image-minimal-1.0-r0 do_rootfs: The postinstall intercept hook
'update_font_cache' failed, details in
Hi folks
When Scott prepares the migration guide for a release, he usually looks to me
to collate the notable changes for it (those requiring user intervention). I
haven't prepared anything yet though and the 2.6 release is fast approaching.
Can anyone who has been involved in or is aware of
On Tuesday, 23 October 2018 11:12:34 PM NZDT Jon Mason wrote:
> A quick grep over all of the native config files shows that of all the
> "#@TYPE: Machine", only one lacks a "#@NAME", mpc8315e-rdb.conf.
>
> It appears that the file OE version of the file has a real name and
> description. See
>
On Tue, Oct 23, 2018 at 2:58 AM, Dhanush K.S wrote:
> Hello Yocto,
>
> I'm currently building an image with the busybox_1.23.2.bb recipe included,
> using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is running on a
> CentOS host building images for the target ARM cortexa8. This busybox
Current Dev Position: YP 2.6 M4.
Next Deadline: YP 2.6 M4 Build Target was Oct. 1, 2018
SWAT Team Rotation:
· SWAT lead is currently: Amanda
· SWAT team rotation: Amanda -> Tracy on Oct. 26, 2018
· SWAT team rotation: Tracy -> Chen on Nov. 2, 2018
·
Hi Yocto,
I am running Yocto 2.5 (Poky Sumo) on the host system CentOS 7.1 to build
images for the target system ARM cortexa8 with a Target_FPU configured to
hard.
I would like to use a Cross Compiler SDK Toolchain in order to build the
images, as the current toolchain fails with a few recipes
Add Bruce.
This is only for v4.18.
Zhe
On 2018/10/23 18:33, zhe...@windriver.com wrote:
> From: He Zhe
>
> unreferenced object 0x9643edb89900 (size 256):
> comm "sd-resolve", pid 220, jiffies 4295016710 (age 208.256s)
> hex dump (first 32 bytes):
> 01 00 00 00 00 00 00 00 03 00 74
From: He Zhe
unreferenced object 0x9643edb89900 (size 256):
comm "sd-resolve", pid 220, jiffies 4295016710 (age 208.256s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 03 00 74 f3 ba b1 b6 b5 ..t.
65 3e 00 00 00 00 00 00 90 f9 a0 ed 43 96 ff ff e>..C...
A quick grep over all of the native config files shows that of all the
"#@TYPE: Machine", only one lacks a "#@NAME", mpc8315e-rdb.conf.
It appears that the file OE version of the file has a real name and
description. See
Hello Yocto,
I'm currently building an image with the busybox_1.23.2.bb recipe included,
using Yocto Sumo 2.5 with the Bitbake version 1.37.0. It is running on a
CentOS host building images for the target ARM cortexa8. This busybox
recipe is placed in another custom layer. Though this recipe
On Mon, Oct 22, 2018 at 11:01 AM Belisko Marek wrote:
>
> Hi Khem,
> On Mon, Oct 22, 2018 at 12:31 AM Khem Raj wrote:
> >
> > On Sun, Oct 21, 2018 at 7:42 PM Belisko Marek
> > wrote:
> > >
> > > Hi Khem,
> > >
> > > On Sun, Oct 21, 2018 at 8:40 PM Khem Raj wrote:
> > > >
> > > >
> > > >
> > >
This helps kernels that might have the sound/soc kconfig changes backported
to 4.14 [1].
This is selected by default by SND_SOC_INTEL_SKL_* configs in 4.14 that are
enabled to be built already in sound.cfg, so this will not result in any
change in behaviour.
[1]
Greetings,
I'm trying to remove the hostapd init file as I'll handle startup of it
on my own. I've created a .bbappend file in my layer to do this:
do_install_append() {
rm -rf ${D}${sysconfdir}/init.d
}
However, this results in a compilation warning when building my image
and
17 matches
Mail list logo
