Add include for Cortex-M4 tunes and nRF52832. The nRF config
appends 'nordic' to MACHINEOVERRIDES, so the kernel recipe
can include Nordic HAL when this override is detected.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@...>
---
conf/machine/include/nrf52832.inc | 10 ++++++++++
conf/machine/include/tune-cortexm4.inc | 19 +++++++++++++++++++
2 files changed, 29 insertions(+)
create mode 100644 conf/machine/include/nrf52832.inc
create mode 100644 conf/machine/include/tune-cortexm4.inc

diff --git a/conf/machine/include/nrf52832.inc b/conf/machine/include/nrf52832.inc
new file mode 100644
index 0000000..73e628a
--- /dev/null
+++ b/conf/machine/include/nrf52832.inc
@@ -0,0 +1,10 @@
+#@TYPE: Machine
+#@NAME: nrf52832
+
+#@DESCRIPTION: Machine configuration for Nordic Semiconductor nRF52832 (Cortex-M4) SoC.
+
+require conf/machine/include/tune-cortexm4.inc
+
+MACHINEOVERRIDES =. "nordic:"
+
+TUNE_FEATURES = "armv7m cortexm4"
diff --git a/conf/machine/include/tune-cortexm4.inc b/conf/machine/include/tune-cortexm4.inc
new file mode 100644
index 0000000..a823b6b
--- /dev/null
+++ b/conf/machine/include/tune-cortexm4.inc
@@ -0,0 +1,19 @@
+DEFAULTTUNE ?= "cortexm4"
+
+require conf/machine/include/arm/arch-armv7a.inc
+
+TUNEVALID[cortexm4] = "Enable Cortex-M4 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'cortexm4', ' -mcpu=cortex-m4', '', d)}"
+AVAILTUNES += "cortexm4"
+
+TUNEVALID[armv7m] = "Enable Cortex-M4 specific processor optimizations"
+TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'armv7m', ' -march=armv7e-m', '', d)}"
+MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'armv7m', 'armv7m:', '' ,d)}"
+
+TUNE_PKGARCH_tune-cortexm4 = "cortexm4"
+
+ARMPKGARCH_tune-cortexm4 = "armv7m"
+PACKAGE_EXTRA_ARCHS_tune-cortexm4 ="cortexm4"
+
+TUNE_FEATURES_tune-cortexm4 = "armv7m vfp cortexm4"
+PACKAGE_EXTRA_ARCHS_tune-cortexm4 = "${PACKAGE_EXTRA_ARCHS_tune-armv7at} armv7m-vfp armv7m"
--
2.25.1

HAL for Nordic chipsets is one of Zephyr subprojects. It is downloaded
by default by west. Clone the HAL repository so it can be used for
building images for boards with Nordic chips.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@...>
---
classes/zephyr-kernel-src.bbclass | 7 ++++---
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 +
2 files changed, 5 insertions(+), 3 deletions(-)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index d245223..ea9b30b 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -5,12 +5,13 @@ PREFERRED_VERSION_zephyr-kernel ??= "2.4.0"
SRCREV_FORMAT = "default_cmsis"
SRCREV_default = "7a3b253ced7333f5c0269387a7f3ed1dee69739d"
SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
-
+SRCREV_nordic = "d8a6ea9695ddf792bb18bb6035c13b1daac5d79c"

SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.4-branch;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
- file://0001-cmake-add-yocto-toolchain.patch \
- "
+ git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
+ file://0001-cmake-add-yocto-toolchain.patch \
+ "

PV = "2.4.0+git${SRCPV}"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index 3f82c20..a1f640d 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -16,6 +16,7 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf"

EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto"
EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
+EXTRA_OECMAKE_append_nordic = "\;${S}/modules/hal/nordic"
export ZEPHYR_BASE="${S}"


--
2.25.1

Hello,

This patch set adds support for the Nitrogen board by 96Boards.
The support consists of:
- adding configs for Cortex-M4, nRF52832 SoC and Nitrogen board,
- adding bbclass with pyocd-based do_flash_usb() implementation.

Tested on Nitrogen and on QEMU so I hope I didn't accidentally
break anything.

Verification:
1. Install pyocd.
2. Connect Nitrogen and make sure you can see Bus 001 Device 004: ID 0d28:0204 NXP ARM mbed
in lsusb.
3. Build a sample app:
$ MACHINE=96b_nitrogen DISTRO=zephyr bitbake zephyr-philosophers
4. Flash app to the board:
$ MACHINE=96b_nitrogen DISTRO=zephyr bitbake zephyr-philosophers -c flash_usb

Wojciech Zmuda (5):
zephyr-kernel: clone Nordic HAL
conf: machine: add support for Nordic nRF52832 Cortex-M4 chip
conf: machine: add 96boards Nitrogen support
zephyr-kernel: don't limit deploy to .elf file
zephyr-flash-pyocd.bbclass: support for flashing via pyocd

README.txt | 23 +++++++++++++++++++
classes/zephyr-flash-pyocd.bbclass | 17 ++++++++++++++
classes/zephyr-kernel-src.bbclass | 7 +++---
conf/machine/96b-nitrogen.conf | 8 +++++++
conf/machine/include/nrf52832.inc | 10 ++++++++
conf/machine/include/tune-cortexm4.inc | 19 +++++++++++++++
.../zephyr-kernel/zephyr-helloworld.bb | 3 ++-
recipes-kernel/zephyr-kernel/zephyr-image.inc | 2 +-
.../zephyr-kernel/zephyr-kernel-common.inc | 5 +++-
.../zephyr-kernel/zephyr-philosophers.bb | 3 ++-
10 files changed, 90 insertions(+), 7 deletions(-)
create mode 100644 classes/zephyr-flash-pyocd.bbclass
create mode 100644 conf/machine/96b-nitrogen.conf
create mode 100644 conf/machine/include/nrf52832.inc
create mode 100644 conf/machine/include/tune-cortexm4.inc

--
2.25.1

Hi Randy

Thank you for your reply.

Doing, "sudo apt install --reinstall coreutils" fixed the problem with test not being found. I'm not sure why it was not on the system, but that error is fixed.

Ah, good.

Unfortunately I've run into another problem when I try and run bitbake, the process fails witht he following error:

 ports/linux/pseudo_wrappers.c:68:16: error: ‘__NR_renameat2’ undeclared (first use in this function)

I'll take another look at that issue in the morning.

You'll need to upgrade to a newer yocto release or cherry-pick:

$ cd ../oe-core.git

$ git log -1 --stat 0fb257121b68f38b40c078150db8f7d0979b7ea5
commit 0fb257121b68f38b40c078150db8f7d0979b7ea5
Author: Richard Purdie <richard.purdie@...>
Date:   Wed Apr 10 19:07:02 2019

    pseudo: Update to gain key bugfixes
   
    Newer distros are using new versions of glibc and coreutils which use the new glibc
    renameat2 function. We need to intercept this for correct functioning of pseudo. This
    is essential to ensure new distros continue to work with the project.
   
    Also, this version has a fix for path/inode cross corruption problems which
    may explain our mysterious locale permissions issues.
   
    Many thanks to Otavio and Peter Seebach for the help in figuring this out and
    fixing it.
   
    Signed-off-by: Richard Purdie <richard.purdie@...>

 meta/recipes-devtools/pseudo/pseudo_git.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

$ git tag --contains 0fb257121b68f38b40c078150db8f7d0979b7ea5
2019-04
2019-04-warrior
2019-04.2-warrior
2019-04.3-warrior
2019-04.4-warrior
2019-10
2019-10-zeus
2019-10.1-zeus
2019-10.2-zeus
2019-10.3-zeus
2019-10.4-zeus
2020-04
2020-04-dunfell
2020-04.1-dunfell
2020-04.2-dunfell
2020-04.3-dunfell
2020-10
2020-10-gatesgarth
uninative-2.5
uninative-2.6
uninative-2.7
uninative-2.8
uninative-2.9
yocto-2.7
yocto-3.0
yocto-3.1
yocto-3.2

../Randy

Andrew

On 05/12/2020 20:27, Randy MacLeod wrote:

On 2020-12-05 2:59 p.m., Andrew Ellis wrote:

Hi Randy

Thank you for your reply.

I'm using Ubuntu 14.04 .

After reading what you said about coreutils in your last message, I tried installing coreutils and got a message saying the latest version is installed. Doing "which test" doesn't yield anything. I've looked in /usr/bin/ and there is no sign of test in there.

The version of Yocto Project I'm using is 2.5 "poky"

Andrew

Andrew,

Thanks for the info about your distro and YP version.

It's odd that 'test' isn't part of your coreutils install.
   https://launchpad.net/ubuntu/trusty/+package/coreutils

Is it possible that you have removed it somehow?
If so you could try:

$ sudo apt install --reinstall coreutils
or
$ sudo apt-get install --reinstall coreutils

../Randy

On 05/12/2020 18:54, Randy MacLeod wrote:

On 2020-12-04 7:08 p.m., ajellisuk via lists.yoctoproject.org wrote:

Hi

I'm trying to compile u-boot for an iMX6 board (iMX6-Q7_Plus from MSC technologies), but the compile process fails with the following output:

    ERROR: Unable to start bitbake server
    ERROR: Last 10 lines of server log for this session
(/home/user/msc-yocto-140/msc-ldk/build/1006/bitbake-cookerdaemon.log):
         self.cooker = bb.cooker.BBCooker(self.configuration,
    self.featureset)
       File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py",
    line 197, in __init__
         self.initConfigurationData()
       File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py",
    line 356, in initConfigurationData
         self.databuilder.parseBaseConfiguration()
       File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cookerdata.py",
    line 317, in parseBaseConfiguration
         raise bb.BBHandledException
    bb.BBHandledException
    ERROR: The following required tools (as specified by HOSTTOOLS)
    appear to be unavailable in PATH, please install them in order to
    proceed:
       test

    ERROR: bitbake u-boot-imx -c compile –f

I have had errors like this before, and have been to resolve by installing the missing tools indicated. The problem that I've got here is that I'm not sure what "test" is referring to. using, "sudo apt-get install test", doesn't work.

Can someone please give me a hint as to what the problem is here.

Hi Andrew,

It seems odd that you don't have coreutils/test already...
Test is part of coreutils on Ubuntu-20.04:

$ which test
/usr/bin/test
$ dpkg -S /usr/bin/test
coreutils: /usr/bin/test

What distro are you using for your build machine and
have you installed the suggested packages?
See the quick start guide and links therein:

https://docs.yoctoproject.org/brief-yoctoprojectqs/brief-yoctoprojectqs.html

https://docs.yoctoproject.org/ref-manual/ref-system-requirements.html#supported-linux-distributions

Also, if you could mention the layers and version of YP code
that you are using that could be helpful in general although
for this issue it shouldn't matter.


../Randy

Thanks in advance

Andrew

-- 
# Randy MacLeod
# Wind River Linux

-- 
# Randy MacLeod
# Wind River Linux

Thanks Tim, for taking this discussion. I'm really glad to see that upstream finally recognizes our use case. Unfortunately as that looks pretty "beta" to me so I will keep on with the tiring process of filing tickets at upstream.
Same goes btw for missing license information in the distribution tarballs (or now upcoming wheels).
Also I'm slightly worried that it will all spiral into requiring always the latest of e.g. setuptools, which could turn into a problem for non-master branches (already have these issue on zeus a lot lately)

I'll take another look at that issue in the morning.

Andrew

Hi Randy

Thank you for your reply.

I'm using Ubuntu 14.04 .

After reading what you said about coreutils in your last message, I tried installing coreutils and got a message saying the latest version is installed. Doing "which test" doesn't yield anything. I've looked in /usr/bin/ and there is no sign of test in there.

The version of Yocto Project I'm using is 2.5 "poky"

Andrew

Andrew,

Thanks for the info about your distro and YP version.

It's odd that 'test' isn't part of your coreutils install.
   https://launchpad.net/ubuntu/trusty/+package/coreutils

Is it possible that you have removed it somehow?
If so you could try:

$ sudo apt install --reinstall coreutils
or
$ sudo apt-get install --reinstall coreutils

../Randy

On 05/12/2020 18:54, Randy MacLeod wrote:

On 2020-12-04 7:08 p.m., ajellisuk via lists.yoctoproject.org wrote:

Hi

I'm trying to compile u-boot for an iMX6 board (iMX6-Q7_Plus from MSC technologies), but the compile process fails with the following output:

    ERROR: Unable to start bitbake server
    ERROR: Last 10 lines of server log for this session
(/home/user/msc-yocto-140/msc-ldk/build/1006/bitbake-cookerdaemon.log):
         self.cooker = bb.cooker.BBCooker(self.configuration,
    self.featureset)
       File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py",
    line 197, in __init__
         self.initConfigurationData()
       File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py",
    line 356, in initConfigurationData
         self.databuilder.parseBaseConfiguration()
       File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cookerdata.py",
    line 317, in parseBaseConfiguration
         raise bb.BBHandledException
    bb.BBHandledException
    ERROR: The following required tools (as specified by HOSTTOOLS)
    appear to be unavailable in PATH, please install them in order to
    proceed:
       test

    ERROR: bitbake u-boot-imx -c compile –f

I have had errors like this before, and have been to resolve by installing the missing tools indicated. The problem that I've got here is that I'm not sure what "test" is referring to. using, "sudo apt-get install test", doesn't work.

Can someone please give me a hint as to what the problem is here.

Hi Andrew,

It seems odd that you don't have coreutils/test already...
Test is part of coreutils on Ubuntu-20.04:

$ which test
/usr/bin/test
$ dpkg -S /usr/bin/test
coreutils: /usr/bin/test

What distro are you using for your build machine and
have you installed the suggested packages?
See the quick start guide and links therein:

https://docs.yoctoproject.org/brief-yoctoprojectqs/brief-yoctoprojectqs.html

https://docs.yoctoproject.org/ref-manual/ref-system-requirements.html#supported-linux-distributions

Also, if you could mention the layers and version of YP code
that you are using that could be helpful in general although
for this issue it shouldn't matter.


../Randy

Thanks in advance

Andrew

-- 
# Randy MacLeod
# Wind River Linux

Hi Randy

Thank you for your reply.

I'm using Ubuntu 14.04 .

After reading what you said about coreutils in your last message, I tried installing coreutils and got a message saying the latest version is installed. Doing "which test" doesn't yield anything. I've looked in /usr/bin/ and there is no sign of test in there.

The version of Yocto Project I'm using is 2.5 "poky"

Andrew

On 2020-12-04 7:08 p.m., ajellisuk via lists.yoctoproject.org wrote:

Hi
I'm trying to compile u-boot for an iMX6 board (iMX6-Q7_Plus from MSC technologies), but the compile process fails with the following output:
ERROR: Unable to start bitbake server
ERROR: Last 10 lines of server log for this session
(/home/user/msc-yocto-140/msc-ldk/build/1006/bitbake-cookerdaemon.log):
    self.cooker = bb.cooker.BBCooker(self.configuration,
self.featureset)
  File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py",
line 197, in __init__
    self.initConfigurationData()
  File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py",
line 356, in initConfigurationData
    self.databuilder.parseBaseConfiguration()
  File
"/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cookerdata.py",
line 317, in parseBaseConfiguration
    raise bb.BBHandledException
bb.BBHandledException
ERROR: The following required tools (as specified by HOSTTOOLS)
appear to be unavailable in PATH, please install them in order to
proceed:
  test
ERROR: bitbake u-boot-imx -c compile –f
I have had errors like this before, and have been to resolve by installing the missing tools indicated. The problem that I've got here is that I'm not sure what "test" is referring to. using, "sudo apt-get install test", doesn't work.
Can someone please give me a hint as to what the problem is here.

Hi Andrew,

It seems odd that you don't have coreutils/test already...
Test is part of coreutils on Ubuntu-20.04:

$ which test
/usr/bin/test
$ dpkg -S /usr/bin/test
coreutils: /usr/bin/test

What distro are you using for your build machine and
have you installed the suggested packages?
See the quick start guide and links therein:

https://docs.yoctoproject.org/brief-yoctoprojectqs/brief-yoctoprojectqs.html

https://docs.yoctoproject.org/ref-manual/ref-system-requirements.html#supported-linux-distributions

Also, if you could mention the layers and version of YP code
that you are using that could be helpful in general although
for this issue it shouldn't matter.


../Randy

Thanks in advance
Andrew

--
# Randy MacLeod
# Wind River Linux

Hi Randy,

Thanks for the reply. I’m using Dunfell 3.1.1 with bitbake version 1.48.0. I had downloaded hostapd recipe from http://layers.openembedded.org/layerindex/recipe/28409/ for my target system i500-pumpkin with mediatek bsp. I had generated an image by adding IMAGE_INSTALL_append = “hostapd” into local.conf and tested on target board. When I run hostapd with default hostapd.conf file I got the mentioned error. 

Thanks & Regards,
VR. 

Hi

I'm trying to compile u-boot for an iMX6 board (iMX6-Q7_Plus from MSC technologies), but the compile process fails with the following output:

ERROR: Unable to start bitbake server
ERROR: Last 10 lines of server log for this session (/home/user/msc-yocto-140/msc-ldk/build/1006/bitbake-cookerdaemon.log):
    self.cooker = bb.cooker.BBCooker(self.configuration, self.featureset)
  File "/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py", line 197, in __init__
    self.initConfigurationData()
  File "/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cooker.py", line 356, in initConfigurationData
    self.databuilder.parseBaseConfiguration()
  File "/home/user/msc-yocto-140/msc-ldk/sources/yocto.git/bitbake/lib/bb/cookerdata.py", line 317, in parseBaseConfiguration
    raise bb.BBHandledException
bb.BBHandledException
ERROR: The following required tools (as specified by HOSTTOOLS) appear to be unavailable in PATH, please install them in order to proceed:
  test

ERROR: bitbake u-boot-imx -c compile –f

I have had errors like this before, and have been to resolve by installing the missing tools indicated. The problem that I've got here is that I'm not sure what "test" is referring to. using, "sudo apt-get install test", doesn't work.

Can someone please give me a hint as to what the problem is here.

Thanks in advance

Andrew

On 2020-12-03 2:02 a.m., vijayrakeshmunganda@... wrote:

Hi All,
Can anyone please help me this issue.

Hi VR,

What version/release of yocto (oe-core, bitbake, ...) are you using?
What image are you building and what did you add to your local.conf ?
What is your target system and who provided the BSP?

If it's an open source bsp layer or you can reproduce the issue using
a layer such as meta-intel or meta-raspberrypi then someone
might be able to help. Otherwise you'll have to contact the BSP vendor.

If you can reproduce the issue with poky, and no one on the list
helps out, then you could open a defect in the YP Bugzilla.

https://wiki.yoctoproject.org/wiki/Bug_reporting_and_Information_levels

Good luck,
../Randy

Thanks &  Regards,
VR

--
# Randy MacLeod
# Wind River Linux

On Fri, Dec 4, 2020 at 3:08 AM <frank.wolff@...> wrote:

Hi,

I've got a weird problem when trying to build perl5 (from perl_5.30.1.bb, "dunfell" branch): the do_install() fails :

rm: cannot remove '/home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so': No such file or directory'

The thing is, there IS a 'libperl.so', which is a symlink, in a "x86_64-linux" subfolder :

$ ls -la /home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so

lrwxrwxrwx 1 frank frank 26 2020-12-04 12:23 /home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/x86_64-linux/CORE/libperl.so -> /usr/lib/libperl.so.5.30.0

And if I try to manually delete it using the same command it works :

& rm /home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so
& ls -la /home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so

zsh: no matches found: /home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so

So... I'm kind of confused to tell the truth. My guess is it's related to my setup (or PEBCAK) or else everybody would have encountered this.

$ uname -a
Linux laptop-frwol 5.9.0-3-amd64 #1 SMP Debian 5.9.9-1 (2020-11-19) x86_64 GNU/Linux

I've made absolutely no modification whatsoever. I've just cloned the "dunfell" branch from poky and launched a "bitbake perl".
Thanks in advance for your help.

Just tried this on Ubuntu 18.04: fresh clone of dunfell branch, source
oe-init-build-env, then bitbake perl

The build was completed successfully, so I am confused too! I do
regular autobuilder runs on debian workers and haven't seen this issue
there either.

Sorry I can't be of more help :-(

Steve

Regards,

Frank.

Thank you, I was able to test build with patch and it does indeed fix my build.

Steve

Hi,

I've got a weird problem when trying to build perl5 (from perl_5.30.1.bb, "dunfell" branch): the do_install() fails :

rm: cannot remove '/home/frwol/Sources/yocto/build/tmp/work/core2-64-poky-linux/perl/5.30.1-r0/image//usr/lib/perl5/5.30.1/*/CORE/libperl.so': No such file or directory'

Hi Maciej Pijanowski, 

Thanks for your suggestion. 

Best regards,
Vijay

On Fri, 2020-12-04 at 12:17 +0000, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:

 
I seem to have an issue initializing busybox.
I have attached my error log… but basically busybox fails to compile
when I set
 
CONFIG_FEATURE_MOUNT_NFS=y
 

The log indicates that it is missing a dependency which ships
"rpc/rpc.h". Some googling turned up this discussion on the
openembedded-core mailing list:

https://lists.openembedded.org/g/openembedded-core/topic/72355602#111216

There is a final patch in the last mail of the topic, but it seems that
this config option is anyway only required for Linux < 2.6.23.

If I modify my_cfg.cfg and remove the above parameter it compiles
clean ,
(I.E. “# CONFIG_FEATURE_MOUNT_NFS is not set”).
 
I am assuming my bbappend file is at fault, but do not see it. This
setup works correctly under “rocko”, and if I disable
“CONFIG_FEATURE_MOUNT_NFS” all appears correct…
 
Can someone tell me what is going on and how to correct ?
 
Thanks,
Steve
 
This is my append file:
 
busybox_%.bbappend:
 
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
FILESEXTRAPATHS_prepend := "${THISDIR}/busybox:"
 
SRC_URI_append += " \
                file://inetd.conf \
                file:// my_cfg.cfg \
                file://ftp.cfg \
                file://ftpd.cfg \
                file://hexdump.cfg \
                file://httpd.cfg \
                file://inetd.cfg \
                file://nc.cfg \
                file://telnetd.cfg \
                file://tftpd.cfg \
                file://coreutils.cfg \
                "
 
PACKAGES =+ "${@plnx_enable_busybox_package('inetd', d)}"
 
INITSCRIPT_PACKAGES =+ "${@plnx_enable_busybox_package('inetd', d)}"
 
FILES_${PN}-inetd = "${sysconfdir}/init.d/busybox-inetd
${sysconfdir}/inetd.conf"
INITSCRIPT_NAME_${PN}-inetd = "inetd.busybox"
INITSCRIPT_PARAMS_${PN}-inetd = "start 65 S ."
CONFFILES_${PN}-inetd = "${sysconfdir}/inetd.conf"
 
RRECOMMENDS_${PN} =+ "${@bb.utils.contains('DISTRO_FEATURES',
'busybox-inetd', '${PN}-inetd', '', d)}"
 
def plnx_enable_busybox_package(f, d):
    distro_features = (d.getVar('DISTRO_FEATURES', True) or
"").split()
    if "busybox-" + f in distro_features:
        return "${PN}-" + f
    else:
        return ""
 
This is my platform specific config file:
 
my_cfg.cfg:
 
CONFIG_EXTRA_COMPAT=y
CONFIG_INCLUDE_SUSv2=y
CONFIG_FEATURE_VERBOSE_USAGE=y
CONFIG_UNICODE_SUPPORT=y
CONFIG_NICE=y
CONFIG_SHA512SUM=y
CONFIG_MKFS_VFAT=y
CONFIG_FEATURE_TOP_SMP_CPU=y
CONFIG_FEATURE_TOP_DECIMALS=y
CONFIG_FEATURE_TOP_SMP_PROCESS=y
CONFIG_FEATURE_TOPMEM=y
CONFIG_FEATURE_MOUNT_VERBOSE=y
CONFIG_FEATURE_MOUNT_HELPERS=y
CONFIG_FEATURE_MOUNT_NFS=y <<<- if disabled, compiles clean
CONFIG_FEATURE_MOUNT_CIFS=y
CONFIG_WATCHDOG=y
CONFIG_DEVMEM=y
CONFIG_LSPCI=y
# CONFIG_GZIP is not set
# CONFIG_GUNZIP is not set
# CONFIG_UNZIP is not set