I wanted to add that it's specifically the glibc development packages which
have this fpu_control.h file conflict.
IMAGE_INSTALL += "glibc-dev"
IMAGE_INSTALL += "lib32-glibc-dev"
-Glenn
From: Stroz, Glenn
Sent: Tuesday, October 11, 2016 4:54 PM
To: 'yocto@yoctop
Hi,
We have a project running an aarch64 compatible processor. For backward
compatibility with some internal software packages, we're using the armv7a-vfp
machine type as a multilib lib32 variant. However, we have found that when
attempting to install both lib32-glibc and glibc we encounter a f
In the busybox.inc recipe include file there are lines where a SysVinit script
should be started when the mdev package is installed:
INITSCRIPT_PACKAGES = "${PN}-httpd ${PN}-syslog ${PN}-udhcpd ${PN}-mdev
${PN}-hwclock"
INITSCRIPT_NAME_${PN}-mdev = "mdev"
INITSCRIPT_PARAMS_${PN}-mdev = "start 0
lenn
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Friday, May 27, 2016 12:20 AM
To: Stroz, Glenn
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] On target gdb support for multiple architectures?
There should be two gdb executables on your target.
On May 26, 2016 3:34 PM, "
Hello,
We're trying to setup our target for onboard debugging. We have multiple
architectures being built with multilib. An armv7 variant which is 32 bit and
an armv8 variant which is 64 bit. We would like the gdb installed in the image
to support both architectures. Right now, even when adding
Thank you – this worked. Got caught up on the idea of multilib being for
libraries only. Using it on binaries worked perfectly.
-Glenn
From: Khem Raj [mailto:raj.k...@gmail.com]
Sent: Thursday, February 11, 2016 9:47 PM
To: Stroz, Glenn
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Selecting
Hi,
We're trying to build a 64 bit arm project. However, one of our applications
needs to be built in 32 bit mode as it isn't supported in 64 bit yet. I've
looked around and it looks like I need to adjust the tuning to be for armv7
instead of the default. However, when I set DEFAULTTUNE in the
