[meta-rockchip][PATCH v3 3/3] linux-yocto: add an initial NanoPi-M4 BSP
Yann Dirson
From: Yann Dirson <yann@...>
This patch provides "standard" and "tiny" BSP. There is still much work to be done in dispatching feature to individual scc files - the more boards we can support the better it will get. Not all SoC/board features are covered yet either (esp. Wifi/Bluetooth an= d audio jack), and properly-woking HDMI still needs patches. Tiny is not fully testable by itself, it can be minimally booted with serial console (though still missing CONFIG_MULTIUSER for serial getty, and CONFIG_INOTIFY_USER for proper udev operation) using: PREFERRED_PROVIDER_virtual/kernel =3D "linux-yocto-tiny" KERNEL_FEATURES_append =3D "\ ktypes/base/base.scc \ features/debug/printk.scc \ cfg/fs/ext4.scc \ cfg/8250.scc \ " Such a tiny build is still using mainline defconfig with lots of hardware features, and the kernel can be slimmed down even more by using: KBUILD_DEFCONFIG =3D "" Kernel weight using default configurations: - standard 11MB - tiny 5MB - tiny with no defconfig 2.5MB Signed-off-by: Yann Dirson <yann@...> --- .../linux/files/bsp/nanopi-m4-standard.scc | 7 ++ .../linux/files/bsp/nanopi-m4-tiny.scc | 7 ++ recipes-kernel/linux/files/bsp/nanopi-m4.cfg | 15 ++++ recipes-kernel/linux/files/bsp/nanopi-m4.scc | 5 ++ recipes-kernel/linux/files/bsp/rk3399.cfg | 71 +++++++++++++++++++ recipes-kernel/linux/files/bsp/rk3399.scc | 5 ++ recipes-kernel/linux/files/bsp/rockchip.cfg | 50 +++++++++++++ recipes-kernel/linux/files/bsp/rockchip.scc | 6 ++ recipes-kernel/linux/linux-yocto%.bbappend | 6 ++ 9 files changed, 172 insertions(+) create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4-standard.scc create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4-tiny.scc create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4.cfg create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4.scc create mode 100644 recipes-kernel/linux/files/bsp/rk3399.cfg create mode 100644 recipes-kernel/linux/files/bsp/rk3399.scc create mode 100644 recipes-kernel/linux/files/bsp/rockchip.cfg create mode 100644 recipes-kernel/linux/files/bsp/rockchip.scc diff --git a/recipes-kernel/linux/files/bsp/nanopi-m4-standard.scc b/reci= pes-kernel/linux/files/bsp/nanopi-m4-standard.scc new file mode 100644 index 0000000..5c74d6b --- /dev/null +++ b/recipes-kernel/linux/files/bsp/nanopi-m4-standard.scc @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +define KMACHINE nanopi-m4 +define KTYPE standard +define KARCH arm + +include ktypes/standard/standard.scc +include nanopi-m4.scc diff --git a/recipes-kernel/linux/files/bsp/nanopi-m4-tiny.scc b/recipes-= kernel/linux/files/bsp/nanopi-m4-tiny.scc new file mode 100644 index 0000000..6e94d6a --- /dev/null +++ b/recipes-kernel/linux/files/bsp/nanopi-m4-tiny.scc @@ -0,0 +1,7 @@ +# SPDX-License-Identifier: MIT +define KMACHINE nanopi-m4 +define KTYPE tiny +define KARCH arm + +include ktypes/tiny/tiny.scc +include nanopi-m4.scc diff --git a/recipes-kernel/linux/files/bsp/nanopi-m4.cfg b/recipes-kerne= l/linux/files/bsp/nanopi-m4.cfg new file mode 100644 index 0000000..7802ab3 --- /dev/null +++ b/recipes-kernel/linux/files/bsp/nanopi-m4.cfg @@ -0,0 +1,15 @@ +CONFIG_MFD_RK808=3Dy +CONFIG_COMMON_CLK_RK808=3Dy + +CONFIG_REGULATOR_RK808=3Dy +CONFIG_REGULATOR_FAN53555=3Dy + +CONFIG_MMC_BLOCK=3Dy +CONFIG_PWRSEQ_SIMPLE=3Dy + +# RTL8211E +CONFIG_REALTEK_PHY=3Dm + +# AP6356S +CONFIG_BT_BCM=3Dm +CONFIG_BT_HCIUART_BCM=3Dy diff --git a/recipes-kernel/linux/files/bsp/nanopi-m4.scc b/recipes-kerne= l/linux/files/bsp/nanopi-m4.scc new file mode 100644 index 0000000..f4267aa --- /dev/null +++ b/recipes-kernel/linux/files/bsp/nanopi-m4.scc @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT + +kconf hardware nanopi-m4.cfg + +include rk3399.scc diff --git a/recipes-kernel/linux/files/bsp/rk3399.cfg b/recipes-kernel/l= inux/files/bsp/rk3399.cfg new file mode 100644 index 0000000..f5f2909 --- /dev/null +++ b/recipes-kernel/linux/files/bsp/rk3399.cfg @@ -0,0 +1,71 @@ +# A72 errata, all past revisions +CONFIG_ARM64_ERRATUM_1319367=3Dy +# A53 errata, all patched on boot when needed +CONFIG_ARM64_ERRATUM_826319=3Dy +CONFIG_ARM64_ERRATUM_827319=3Dy +CONFIG_ARM64_ERRATUM_824069=3Dy +CONFIG_ARM64_ERRATUM_819472=3Dy + +# cru +CONFIG_CLK_RK3399=3Dy + +CONFIG_PL330_DMA=3Dy +CONFIG_I2C_RK3X=3Dy +CONFIG_SERIAL_8250_DW=3Dy + +# usb +CONFIG_PHY_ROCKCHIP_INNO_USB2=3Dy +CONFIG_PHY_ROCKCHIP_TYPEC=3Dy + +# ethernet +CONFIG_NET_VENDOR_STMICRO=3Dy +CONFIG_STMMAC_ETH=3Dm +CONFIG_STMMAC_PLATFORM=3Dm +CONFIG_DWMAC_ROCKCHIP=3Dm +CONFIG_PHYLIB=3Dm + +# display +CONFIG_ROCKCHIP_DW_HDMI=3Dy +CONFIG_ROCKCHIP_DW_MIPI_DSI=3Dy +CONFIG_ROCKCHIP_ANALOGIX_DP=3Dy +CONFIG_ROCKCHIP_CDN_DP=3Dy +CONFIG_PHY_ROCKCHIP_DP=3Dy +CONFIG_DRM_DW_HDMI=3Dm +CONFIG_DRM_DW_HDMI_I2S_AUDIO=3Dm +CONFIG_DRM_DW_HDMI_CEC=3Dm +CONFIG_DRM_DW_MIPI_DSI=3Dm +CONFIG_DRM_PANFROST=3Dm + +# HDMI audio +CONFIG_DRM_DW_HDMI_AHB_AUDIO=3Dm +CONFIG_SND_SOC_RK3288_HDMI_ANALOG=3Dm + +CONFIG_VIDEO_DEV=3Dm +CONFIG_V4L_MEM2MEM_DRIVERS=3Dy +CONFIG_VIDEO_ROCKCHIP_RGA=3Dm + +CONFIG_V4L2_H264=3Dm +CONFIG_MEDIA_CONTROLLER_REQUEST_API=3Dy +CONFIG_VIDEO_HANTRO=3Dm +CONFIG_VIDEO_HANTRO_ROCKCHIP=3Dy +CONFIG_VIDEO_ROCKCHIP_VDEC=3Dm + +# usb +CONFIG_USB_DWC2=3Dy +CONFIG_USB_DWC3=3Dy +CONFIG_USB_DWC3_DUAL_ROLE=3Dy + +# sd/mmc +CONFIG_MMC=3Dy +CONFIG_MMC_SDHCI=3Dy +CONFIG_MMC_SDHCI_PLTFM=3Dy +CONFIG_MMC_DW=3Dy +CONFIG_MMC_DW_ROCKCHIP=3Dy +CONFIG_MMC_SDHCI_OF_ARASAN=3Dy + +# temperature sensors +CONFIG_THERMAL=3Dy +CONFIG_THERMAL_OF=3Dy +CONFIG_ROCKCHIP_THERMAL=3Dm +CONFIG_IIO=3Dy +CONFIG_ROCKCHIP_SARADC=3Dm diff --git a/recipes-kernel/linux/files/bsp/rk3399.scc b/recipes-kernel/l= inux/files/bsp/rk3399.scc new file mode 100644 index 0000000..9b1a88e --- /dev/null +++ b/recipes-kernel/linux/files/bsp/rk3399.scc @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT + +kconf hardware rk3399.cfg + +include rockchip.scc diff --git a/recipes-kernel/linux/files/bsp/rockchip.cfg b/recipes-kernel= /linux/files/bsp/rockchip.cfg new file mode 100644 index 0000000..05a397d --- /dev/null +++ b/recipes-kernel/linux/files/bsp/rockchip.cfg @@ -0,0 +1,50 @@ +CONFIG_CPU_ISOLATION=3Dy +CONFIG_NUMA_BALANCING_DEFAULT_ENABLED=3Dy +CONFIG_HZ_250=3Dy +CONFIG_CPU_IDLE=3Dy +CONFIG_ARM_CPUIDLE=3Dy + +CONFIG_ARCH_ROCKCHIP=3Dy +CONFIG_COMMON_CLK_ROCKCHIP=3Dy +CONFIG_REGULATOR=3Dy +CONFIG_REGULATOR_FIXED_VOLTAGE=3Dy +CONFIG_REGULATOR_PWM=3Dy +CONFIG_I2C=3Dy +CONFIG_FW_LOADER=3Dy +CONFIG_PHY_ROCKCHIP_EMMC=3Dy +CONFIG_PINCTRL=3Dy +CONFIG_PINCTRL_ROCKCHIP=3Dy +CONFIG_ROCKCHIP_IODOMAIN=3Dy +CONFIG_ROCKCHIP_PM_DOMAINS=3Dy + +CONFIG_SPI=3Dy +CONFIG_SPI_ROCKCHIP=3Dm + +CONFIG_PWM=3Dy +CONFIG_PWM_ROCKCHIP=3Dy + +CONFIG_DRM_KMS_HELPER=3Dm +CONFIG_DRM_FBDEV_EMULATION=3Dy +CONFIG_ROCKCHIP_IOMMU=3Dy +CONFIG_DRM_ROCKCHIP=3Dm +CONFIG_DRM_BRIDGE=3Dy + +CONFIG_SND=3Dy +CONFIG_SND_SOC=3Dy +CONFIG_SND_HDA_CODEC_HDMI=3Dm +CONFIG_SND_SOC_ROCKCHIP=3Dm +CONFIG_SND_SOC_ROCKCHIP_I2S=3Dm +CONFIG_SND_SOC_ROCKCHIP_SPDIF=3Dm + +CONFIG_NVMEM=3Dy +CONFIG_ROCKCHIP_EFUSE=3Dm + +CONFIG_CPU_FREQ=3Dy +CONFIG_CPU_FREQ_THERMAL=3Dy +CONFIG_HWMON=3Dy +CONFIG_THERMAL_HWMON=3Dy + +CONFIG_CRYPTO_HW=3Dy +CONFIG_CRYPTO_DEV_ROCKCHIP=3Dm + +CONFIG_MMC_BLOCK_MINORS=3D32 diff --git a/recipes-kernel/linux/files/bsp/rockchip.scc b/recipes-kernel= /linux/files/bsp/rockchip.scc new file mode 100644 index 0000000..800f105 --- /dev/null +++ b/recipes-kernel/linux/files/bsp/rockchip.scc @@ -0,0 +1,6 @@ +# SPDX-License-Identifier: MIT + +kconf hardware rockchip.cfg + +include cfg/dmaengine.scc +include features/mmc/mmc-block.cfg diff --git a/recipes-kernel/linux/linux-yocto%.bbappend b/recipes-kernel/= linux/linux-yocto%.bbappend index 7702e3f..9658681 100644 --- a/recipes-kernel/linux/linux-yocto%.bbappend +++ b/recipes-kernel/linux/linux-yocto%.bbappend @@ -1,3 +1,9 @@ +FILESEXTRAPATHS_prepend :=3D "${THISDIR}/files:" + +SRC_URI_append =3D "\ + file://bsp;type=3Dkmeta;subdir=3Dkernel-meta \ +" + COMPATIBLE_MACHINE_marsboard-rk3066 =3D "marsboard-rk3066" COMPATIBLE_MACHINE_rock2-square =3D "rock2-square" COMPATIBLE_MACHINE_radxarock =3D "radxarock" --=20 2.30.2
|
|
[meta-rockchip][PATCH v3 2/3] NanoPi-M4: declare "usbhost" in MACHINE_FEATURES
Yann Dirson
From: Yann Dirson <yann@...>
Lets USB tools be installed if the distro activates the feature. Signed-off-by: Yann Dirson <yann@...> --- conf/machine/include/nanopi-m4.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/na= nopi-m4.inc index 603160f..1a16eae 100644 --- a/conf/machine/include/nanopi-m4.inc +++ b/conf/machine/include/nanopi-m4.inc @@ -3,6 +3,8 @@ =20 require rk3399.inc =20 +MACHINE_FEATURES +=3D "usbhost" + KMACHINE =3D "nanopi-m4" KERNEL_DEVICETREE =3D "rockchip/rk3399-nanopi-m4.dtb" =20 --=20 2.30.2
|
|
[meta-rockchip][PATCH v3 0/3] kmeta BSP for nanopi-m4
Yann Dirson
From: Yann Dirson <yann@...>
Changes from in v3: - relocate the bsp files into files/ so we don't have to add linux-yocto/ to FILESEXTRAPATHS for all other kernels - removed the "don't force KCONFIG_MODE to alldefconfig" (not needed fina= lly, and causing interferences in default setup) - add "usbhost" to MACHINE_FEATURES to enable lsusb and friends - better hardware coverage (though still no wifi/bt/audio, and buggy hdmi= ) The Wifi/BT support requires firmware, to be properly packaged; BT support itself is still buggy in mainline; audio jack requires a couple of patches; HDMI requires at the very least a DTS patch, and LibreELEC maintains a "latest and greatest" DRM patchset, but it can conflicts with some patches in default kmeta. Yann Dirson (3): rockchip-defaults: don't force KCONFIG_MODE to alldefconfig NanoPi-M4: let all variants use the same KMACHINE type linux-yocto: add a NanoPi-M4 BSP conf/machine/include/nanopi-m4.inc | 1 + conf/machine/include/rockchip-defaults.inc | 1 - .../linux/files/bsp/nanopi-m4-standard.scc | 7 +++ .../linux/files/bsp/nanopi-m4-tiny.scc | 7 +++ recipes-kernel/linux/files/bsp/nanopi-m4.cfg | 40 ++++++++++++++ recipes-kernel/linux/files/bsp/nanopi-m4.scc | 5 ++ recipes-kernel/linux/files/bsp/rk3399.cfg | 50 +++++++++++++++++ recipes-kernel/linux/files/bsp/rk3399.scc | 5 ++ recipes-kernel/linux/files/bsp/rockchip.cfg | 53 +++++++++++++++++++ recipes-kernel/linux/files/bsp/rockchip.scc | 6 +++ recipes-kernel/linux/linux-yocto%.bbappend | 6 +++ 11 files changed, 180 insertions(+), 1 deletion(-) create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4-standard.scc create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4-tiny.scc create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4.cfg create mode 100644 recipes-kernel/linux/files/bsp/nanopi-m4.scc create mode 100644 recipes-kernel/linux/files/bsp/rk3399.cfg create mode 100644 recipes-kernel/linux/files/bsp/rk3399.scc create mode 100644 recipes-kernel/linux/files/bsp/rockchip.cfg create mode 100644 recipes-kernel/linux/files/bsp/rockchip.scc --=20 2.30.2
|
|
[meta-rockchip][PATCH v3 1/3] NanoPi-M4: let all variants use the same KMACHINE type
Yann Dirson
From: Yann Dirson <yann@...>
This will allow us to define a single set of kernel BSP for all variants of the board (which only need to differ in u-boot dts). Signed-off-by: Yann Dirson <yann@...> --- conf/machine/include/nanopi-m4.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/machine/include/nanopi-m4.inc b/conf/machine/include/na= nopi-m4.inc index 74cdae8..603160f 100644 --- a/conf/machine/include/nanopi-m4.inc +++ b/conf/machine/include/nanopi-m4.inc @@ -3,6 +3,7 @@ =20 require rk3399.inc =20 +KMACHINE =3D "nanopi-m4" KERNEL_DEVICETREE =3D "rockchip/rk3399-nanopi-m4.dtb" =20 RK_BOOT_DEVICE =3D "mmcblk1" --=20 2.30.2
|
|
Monsees, Steven C (US)
Thanks you...
toggle quoted messageShow quoted text
-----Original Message-----
From: Khem Raj <raj.khem@...> Sent: Thursday, April 22, 2021 11:23 PM To: Monsees, Steven C (US) <steven.monsees@...> Cc: yocto@... Subject: Re: [yocto] #yocto #sdk #cmake External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access "Cybersecurity OneSpace Page" and report phishing by clicking the button "Report Phishing" on the Outlook toolbar. take a look at https://github.com/kraj/meta-clang/blob/master/recipes-core/meta/clang-environment.inc#L11-L19 perhaps that can be something you might find useful On Thu, Apr 22, 2021 at 11:51 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:
|
|
Re: #bitbake Can't use 'bitbake -g <image-name> -u taskdep
#bitbake
keydi <krzysztof.dudziak@...>
As for project here Poky operates on headless server. Developers use SSH to interact with Poky, to handle its input data, and to access build results. Must gtk3 be installed locally to Poky or will taskexp be able to connect to gtk3 operating on ssh client? As of time being Poky host has gtk not installed. Installation of gtk on Poky host will need approval of latter's administrator.
|
|
Re: Problems building hardknott for raspberri pi
On Thu, Apr 22, 2021 at 11:13 PM Morten Bruun <morten.bruun@...> wrote:
Then it should not be using Mesa-gl so it’s a bit confusing how you end up needing it
|
|
Re: Problems building hardknott for raspberri pi
Morten Bruun
On Fri, Apr 23, 2021 at 8:03 AM Khem Raj <raj.khem@...> wrote: On Thu, Apr 22, 2021 at 10:54 PM Morten Bruun <morten.bruun@...> wrote: No, I'm not using DISABLE_VC4GRAPHICS - should I? /Morten
|
|
Re: Problems building hardknott for raspberri pi
On Thu, Apr 22, 2021 at 10:54 PM Morten Bruun <morten.bruun@...> wrote:
never mind, I think we perhaps have is broken on master too. Are you using DISABLE_VC4GRAPHICS = "1" ? ERROR: mesa-gl-2_21.0.1-r0 do_configure: meson failed
|
|
Re: Problems building hardknott for raspberri pi
Morten Bruun
On Fri, Apr 23, 2021 at 7:30 AM Khem Raj <raj.khem@...> wrote: On Thu, Apr 22, 2021 at 10:22 PM Morten Bruun <morten.bruun@...> wrote: Thanks for your quick reply. I tried to build with d1f191ed3018e0b130311e443f014e30d2f5ed97 which gives me this error instead: ERROR: mesa-gl-2_21.0.1-r0 do_configure: meson failed ERROR: mesa-gl-2_21.0.1-r0 do_configure: Execution of '/home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_configure.32301' failed with exit code 1:The Meson build system Version: 0.57.1 Source dir: /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/mesa-21.0.1 Build dir: /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/build Build type: cross build Program python3 found: YES (/home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot-native/usr/bin/python3-native/python3) ../mesa-21.0.1/meson.build:21:0: ERROR: Options "swrast" are not in allowed choices: "auto, i915, i965, r100, r200, nouveau" A full log can be found at /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/build/meson-logs/meson-log.txt WARNING: /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_configure.32301:181 exit 1 from 'exit 1' WARNING: Backtrace (BB generated script): #1: bbfatal_log, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_configure.32301, line 181 #2: meson_do_configure, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_configure.32301, line 170 #3: do_configure, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_configure.32301, line 156 #4: main, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_configure.32301, line 194 Backtrace (metadata-relative locations): #1: bbfatal_log, /home/morten/vetscan-spe-instrument/poky/meta/classes/logging.bbclass, line 72 #2: meson_do_configure, /home/morten/vetscan-spe-instrument/poky/meta/classes/meson.bbclass, line 160 #3: do_configure, autogenerated, line 2 ERROR: Logfile of failure stored in: /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/log.do_configure.32301
|
|
Re: Problems building hardknott for raspberri pi
On Thu, Apr 22, 2021 at 10:22 PM Morten Bruun <morten.bruun@...> wrote:
I think meta-raspberrypi should branch before mesa-gl restructuring initiated changes in meta-raspberrypi can you try with meta-raspberrypi master@d1f191ed3018e0b130311e443f014e30d2f5ed97 and see if it works Does anyone know why this error occurs when building mesa-gl?
|
|
Problems building hardknott for raspberri pi
Morten Bruun
Hi, I'm upgrading to hardknott. The meta-raspberry layer does not have a hardknott branch, so I'm building with the master branch. Does anyone know why this error occurs when building mesa-gl? ERROR: mesa-gl-2_21.0.1-r0 do_compile: Execution of '/home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_compile.31992' failed with exit code 1: [1/7] arm-poky-linux-gnueabi-g++ -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot -o src/gbm/libgbm.so.1.0.0 src/gbm/libgbm.so.1.0.0.p/main_backend.c.o src/gbm/libgbm.so.1.0.0.p/main_gbm.c.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libgbm.so.1 -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,relro,-z,now src/loader/libloader.a src/util/libmesa_util.a src/util/format/libmesa_format.a src/util/libxmlconfig.a -Wl,--gc-sections -ldl -pthread /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot/usr/lib/libz.so -lm /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot/usr/lib/libexpat.so /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot/usr/lib/libdrm.so -Wl,--end-group FAILED: src/gbm/libgbm.so.1.0.0 arm-poky-linux-gnueabi-g++ -mthumb -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security --sysroot=/home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot -o src/gbm/libgbm.so.1.0.0 src/gbm/libgbm.so.1.0.0.p/main_backend.c.o src/gbm/libgbm.so.1.0.0.p/main_gbm.c.o -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,--start-group -Wl,-soname,libgbm.so.1 -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-z,relro,-z,now src/loader/libloader.a src/util/libmesa_util.a src/util/format/libmesa_format.a src/util/libxmlconfig.a -Wl,--gc-sections -ldl -pthread /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot/usr/lib/libz.so -lm /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot/usr/lib/libexpat.so /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot/usr/lib/libdrm.so -Wl,--end-group /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/ld: src/gbm/libgbm.so.1.0.0.p/main_backend.c.o: in function `_gbm_create_device': /usr/src/debug/mesa-gl/2_21.0.1-r0/build/../mesa-21.0.1/src/gbm/main/backend.c:104: undefined reference to `gbm_dri_backend' collect2: error: ld returned 1 exit status [2/7] /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/recipe-sysroot-native/usr/bin/python3-native/python3 ../mesa-21.0.1/bin/git_sha1_gen.py --output src/git_sha1.h [3/4] rm -f src/mesa/libmesa_classic.a && arm-poky-linux-gnueabi-gcc-ar csrD src/mesa/libmesa_classic.a src/mesa/libmesa_classic.a.p/math_m_xform.c.o src/mesa/libmesa_classic.a.p/tnl_t_context.c.o src/mesa/libmesa_classic.a.p/tnl_t_draw.c.o src/mesa/libmesa_classic.a.p/tnl_t_pipeline.c.o src/mesa/libmesa_classic.a.p/tnl_t_rebase.c.o src/mesa/libmesa_classic.a.p/tnl_t_split.c.o src/mesa/libmesa_classic.a.p/tnl_t_split_copy.c.o src/mesa/libmesa_classic.a.p/tnl_t_split_inplace.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_fog.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_light.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_normals.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_points.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_program.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_render.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_texgen.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_texmat.c.o src/mesa/libmesa_classic.a.p/tnl_t_vb_vertex.c.o src/mesa/libmesa_classic.a.p/tnl_t_vertex.c.o src/mesa/libmesa_classic.a.p/tnl_t_vertex_generic.c.o src/mesa/libmesa_classic.a.p/tnl_t_vertex_sse.c.o src/mesa/libmesa_classic.a.p/tnl_t_vp_build.c.o src/mesa/libmesa_classic.a.p/swrast_s_aaline.c.o src/mesa/libmesa_classic.a.p/swrast_s_aatriangle.c.o src/mesa/libmesa_classic.a.p/swrast_s_alpha.c.o src/mesa/libmesa_classic.a.p/swrast_s_atifragshader.c.o src/mesa/libmesa_classic.a.p/swrast_s_bitmap.c.o src/mesa/libmesa_classic.a.p/swrast_s_blend.c.o src/mesa/libmesa_classic.a.p/swrast_s_blit.c.o src/mesa/libmesa_classic.a.p/swrast_s_clear.c.o src/mesa/libmesa_classic.a.p/swrast_s_context.c.o src/mesa/libmesa_classic.a.p/swrast_s_copypix.c.o src/mesa/libmesa_classic.a.p/swrast_s_depth.c.o src/mesa/libmesa_classic.a.p/swrast_s_drawpix.c.o src/mesa/libmesa_classic.a.p/swrast_s_feedback.c.o src/mesa/libmesa_classic.a.p/swrast_s_fog.c.o src/mesa/libmesa_classic.a.p/swrast_s_fragprog.c.o src/mesa/libmesa_classic.a.p/swrast_s_lines.c.o src/mesa/libmesa_classic.a.p/swrast_s_logic.c.o src/mesa/libmesa_classic.a.p/swrast_s_masking.c.o src/mesa/libmesa_classic.a.p/swrast_s_points.c.o src/mesa/libmesa_classic.a.p/swrast_s_renderbuffer.c.o src/mesa/libmesa_classic.a.p/swrast_s_span.c.o src/mesa/libmesa_classic.a.p/swrast_s_stencil.c.o src/mesa/libmesa_classic.a.p/swrast_s_texcombine.c.o src/mesa/libmesa_classic.a.p/swrast_s_texfetch.c.o src/mesa/libmesa_classic.a.p/swrast_s_texfilter.c.o src/mesa/libmesa_classic.a.p/swrast_s_texrender.c.o src/mesa/libmesa_classic.a.p/swrast_s_texture.c.o src/mesa/libmesa_classic.a.p/swrast_s_triangle.c.o src/mesa/libmesa_classic.a.p/swrast_s_zoom.c.o src/mesa/libmesa_classic.a.p/swrast_setup_ss_context.c.o src/mesa/libmesa_classic.a.p/swrast_setup_ss_triangle.c.o src/mesa/libmesa_classic.a.p/drivers_common_driverfuncs.c.o src/mesa/libmesa_classic.a.p/drivers_common_meta_blit.c.o src/mesa/libmesa_classic.a.p/drivers_common_meta_generate_mipmap.c.o src/mesa/libmesa_classic.a.p/drivers_common_meta.c.o src/mesa/libmesa_classic.a.p/x86_x86_xform.c.o src/mesa/libmesa_classic.a.p/x86_3dnow.c.o src/mesa/libmesa_classic.a.p/x86_sse.c.o src/mesa/libmesa_classic.a.p/x86_rtasm_x86sse.c.o src/mesa/libmesa_classic.a.p/sparc_sparc.c.o src/mesa/libmesa_classic.a.p/x86-64_x86-64.c.o ninja: build stopped: subcommand failed. WARNING: /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_compile.31992:161 exit 1 from 'ninja -v -j 8' WARNING: Backtrace (BB generated script): #1: meson_do_compile, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_compile.31992, line 161 #2: do_compile, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_compile.31992, line 156 #3: main, /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/run.do_compile.31992, line 165 Backtrace (metadata-relative locations): #1: meson_do_compile, /home/morten/vetscan-spe-instrument/poky/meta/classes/meson.bbclass, line 176 #2: do_compile, autogenerated, line 2 ERROR: Logfile of failure stored in: /home/morten/yocto/spe/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/mesa-gl/2_21.0.1-r0/temp/log.do_compile.31992
|
|
take a look at
toggle quoted messageShow quoted text
https://github.com/kraj/meta-clang/blob/master/recipes-core/meta/clang-environment.inc#L11-L19 perhaps that can be something you might find useful On Thu, Apr 22, 2021 at 11:51 AM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:
|
|
Re: [meta-openssl102-fips][PATCH 0/6] hardknott fixes
Jason Wessel <jason.wessel@...>
Merged.
toggle quoted messageShow quoted text
On 4/22/21 1:56 AM, Yi Zhao wrote:
|
|
Monsees, Steven C (US)
When setting up an SDK, (standard or extensible), build which will be using cmake, is there a proper way to pre-configure OEToolchainConfig.cmake for ones env/applications ?
Currently I build the SDK, install, and then manually edit…
Thanks, Steve
|
|
Re: #bitbake Can't use 'bitbake -g <image-name> -u taskdep
#bitbake
Ross Burton <ross@...>
Basically, taskdep needs gobject-introspection and gtk3 on the host.
toggle quoted messageShow quoted text
You're most likely missing the GTK3 gir files. Ross
On Thu, 22 Apr 2021 at 17:00, keydi <krzysztof.dudziak@...> wrote:
|
|
Re: #bitbake Can't use 'bitbake -g <image-name> -u taskdep
#bitbake
keydi <krzysztof.dudziak@...>
If yes, me wonders how to force Bitbake to build that recipe, if for target system gtk is not built, there is actually no target depending on gtk. Hence, I add such recipe Bitbake might ignore it as target system image does not order, nor any other target depends on.
|
|
Re: #bitbake Can't use 'bitbake -g <image-name> -u taskdep
#bitbake
keydi <krzysztof.dudziak@...>
Myself wonders if the answer is just to enable a recipe building native package gtk of version 3.0.
|
|
Re: [meta-security][PATCH] packagegroup-core-security: exclude apparmor in mips64
On 4/20/21 9:07 AM, Khem Raj wrote:
Actuall, this is the wrong patch. working on too many systems. Thanks for the review. -armin RDEPENDS_packagegroup-meta-security-ptest-packages = "\
|
|
Re: [PATCH] [yocto-autobuilder-helper 1/2] config.json: Add default MACHINE qemux86-64
Yi Fan Yu
+cc RP
toggle quoted messageShow quoted text
On 4/19/21 10:36 PM, Yi Fan Yu wrote:
This is the default oe-core MACHINE value.
|
|