Date   

[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


Re: #yocto #sdk #cmake #yocto #sdk #cmake

Monsees, Steven C (US)
 

Thanks you...

-----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:



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

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

Khem Raj
 



On Thu, Apr 22, 2021 at 11:13 PM Morten Bruun <morten.bruun@...> wrote:
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:
>
> 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:
>> >
>> > I'm upgrading to hardknott. The meta-raspberry layer does not have a hardknott branch, so I'm building with the master branch.
>> >
>>
>> 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
>>
> Thanks for your quick reply. I tried to build with d1f191ed3018e0b130311e443f014e30d2f5ed97 which gives me this error instead:
>

never mind, I think we perhaps have is broken on master too. Are you
using DISABLE_VC4GRAPHICS = "1" ?


No, I'm not using DISABLE_VC4GRAPHICS - should I?

Then it should not be using Mesa-gl so it’s a bit confusing how you end up needing it 


/Morten


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:
>
> 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:
>> >
>> > I'm upgrading to hardknott. The meta-raspberry layer does not have a hardknott branch, so I'm building with the master branch.
>> >
>>
>> 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
>>
> Thanks for your quick reply. I tried to build with d1f191ed3018e0b130311e443f014e30d2f5ed97 which gives me this error instead:
>

never mind, I think we perhaps have is broken on master too. Are you
using DISABLE_VC4GRAPHICS = "1" ?


No, I'm not using DISABLE_VC4GRAPHICS - should I?

/Morten


Re: Problems building hardknott for raspberri pi

Khem Raj
 

On Thu, Apr 22, 2021 at 10:54 PM Morten Bruun <morten.bruun@...> wrote:

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:

I'm upgrading to hardknott. The meta-raspberry layer does not have a hardknott branch, so I'm building with the master branch.
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
Thanks for your quick reply. I tried to build with d1f191ed3018e0b130311e443f014e30d2f5ed97 which gives me this error instead:
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
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

-- Morten


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:
>
> I'm upgrading to hardknott. The meta-raspberry layer does not have a hardknott branch, so I'm building with the master branch.
>

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

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

-- Morten


Re: Problems building hardknott for raspberri pi

Khem Raj
 

On Thu, Apr 22, 2021 at 10:22 PM Morten Bruun <morten.bruun@...> wrote:

Hi,

I'm upgrading to hardknott. The meta-raspberry layer does not have a hardknott branch, so I'm building with the master branch.
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?

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

-- Morten



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

-- Morten


Re: #yocto #sdk #cmake #yocto #sdk #cmake

Khem Raj
 

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:




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: [meta-openssl102-fips][PATCH 0/6] hardknott fixes

Jason Wessel <jason.wessel@...>
 

Merged.

On 4/22/21 1:56 AM, Yi Zhao wrote:

Changqing Li (1):
openssh: refresh patches to 8.5p1

Chen Qi (1):
layer.conf: add hardknott to LAYERSERIES_COMPAT

Yi Zhao (4):
README.build: add "Known Issues" section
openssh: refresh patches to 8.4p1
openssh: fix the double free error for ssh-cavs
openssh: set kex->sessin_id via sshbuf_put in ssh-cavs

README.build | 28 +++
conf/layer.conf | 2 +-
.../0001-conditional-enable-fips-mode.patch | 46 ++---
...ps.patch => 0001-openssh-8.4p1-fips.patch} | 173 +++++++-----------
...1-ssh-cavs-fix-the-double-free-error.patch | 161 ++++++++++++++++
...avs-set-kex-sessin_id-via-sshbuf_put.patch | 45 +++++
recipes-connectivity/openssh/openssh_fips.inc | 4 +-
7 files changed, 327 insertions(+), 132 deletions(-)
rename recipes-connectivity/openssh/openssh/{0001-openssh-8.2p1-fips.patch => 0001-openssh-8.4p1-fips.patch} (73%)
create mode 100644 recipes-connectivity/openssh/openssh/0001-ssh-cavs-fix-the-double-free-error.patch
create mode 100644 recipes-connectivity/openssh/openssh/0001-ssh-cavs-set-kex-sessin_id-via-sshbuf_put.patch


#yocto #sdk #cmake #yocto #sdk #cmake

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.
You're most likely missing the GTK3 gir files.

Ross

On Thu, 22 Apr 2021 at 17:00, keydi <krzysztof.dudziak@...> wrote:

Myself wonders if the answer is just to enable a recipe building native package gtk of version 3.0.


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

Armin Kuster
 

On 4/20/21 9:07 AM, Khem Raj wrote:


On 4/20/21 7:41 AM, Armin Kuster wrote:
Signed-off-by: Armin Kuster <akuster808@...>
---
  recipes-core/packagegroup/packagegroup-core-security.bb | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/recipes-core/packagegroup/packagegroup-core-security.bb
b/recipes-core/packagegroup/packagegroup-core-security.bb
index 9ac0d2c..a6142a8 100644
--- a/recipes-core/packagegroup/packagegroup-core-security.bb
+++ b/recipes-core/packagegroup/packagegroup-core-security.bb
@@ -80,6 +80,9 @@ RDEPENDS_packagegroup-security-mac = " \
      ${@bb.utils.contains("DISTRO_FEATURES", "smack", "smack", "",d)} \
      "
  +RDEPENDS_packagegroup-security-mac_remove_mips64 = "apparmor"
+RDEPENDS_packagegroup-security-mac_remove_mips64le = "apparmor"
+
this should be mips64el
Actuall, this is the wrong patch. working on too many systems.

Thanks for the review.

-armin

  RDEPENDS_packagegroup-meta-security-ptest-packages = "\
      ptest-runner \
      samhain-standalone-ptest \





Re: [PATCH] [yocto-autobuilder-helper 1/2] config.json: Add default MACHINE qemux86-64

Yi Fan Yu
 

+cc RP

On 4/19/21 10:36 PM, Yi Fan Yu wrote:
This is the default oe-core MACHINE value.
Prevent error-reporting tool to report simply False.
It was seen in check-layer where the MACHINE wasn't specified.
[YOCTO #14208]
Signed-off-by: Yi Fan Yu <yifan.yu@...>
---
config.json | 1 +
1 file changed, 1 insertion(+)
diff --git a/config.json b/config.json
index 962d8ae..2d1a698 100644
--- a/config.json
+++ b/config.json
@@ -26,6 +26,7 @@
"defaults" : {
"NEEDREPOS" : ["poky"],
"DISTRO" : "poky",
+ "MACHINE" : "qemux86-64",
"SDKMACHINE" : "i686",
"PACKAGE_CLASSES" : "package_rpm package_deb package_ipk",
"DLDIR" : "DL_DIR = '${BASE_SHAREDDIR}/current_sources'",


[yocto-autobuilder2] [PATCH] config/schedulers: Add check-layer-nightly

Richard Purdie
 

Add a new target to run layer checks every 24 hours on various layers we don't
test as part of the standard test runs.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
config.py | 2 ++
schedulers.py | 5 +++++
2 files changed, 7 insertions(+)

diff --git a/config.py b/config.py
index 54ec9ce8..82076cd3 100644
--- a/config.py
+++ b/config.py
@@ -23,6 +23,7 @@ buildertorepos = {
"qemuarm-oecore": ["oecore", "bitbake"],
"checkuri": ["poky"],
"check-layer": ["poky", "meta-mingw", "meta-gplv2"],
+ "check-layer-nightly": ["poky", "meta-agl", "meta-arm", "meta-aws", "meta-intel", "meta-openembedded", "meta-virtualization"],
"docs": ["yocto-docs", "bitbake"],
"default": ["poky"]
}
@@ -110,6 +111,7 @@ builders_others = [
"qemuarm-armhost",
"meta-agl-core",
"meta-aws",
+ "check-layer-nightly",
"auh"
]

diff --git a/schedulers.py b/schedulers.py
index 9d81806b..8b166e0b 100644
--- a/schedulers.py
+++ b/schedulers.py
@@ -352,6 +352,11 @@ schedulers.append(sched.Nightly(name='nightly-quick', branch='master', propertie
schedulers.append(sched.Nightly(name='nightly-full', branch='master', properties=parent_default_props('a-full'),
builderNames=['a-full'], hour=1, minute=0, dayOfWeek=6))

+# Run check-layer-nightly each day
+schedulers.append(sched.Nightly(name='nightly-check-layer', branch='master', properties=parent_default_props('check-layer-nightly'),
+ builderNames=['check-layer-nightly'], hour=0, minute=0))
+
+
# Run the build performance tests at 3am, 9am, 3pm and 9pm
schedulers.append(sched.Nightly(name='nightly-buildperf-ubuntu1604', branch='master', properties=parent_default_props('buildperf-ubuntu1604'),
builderNames=['buildperf-ubuntu1604'], hour=[3,9,15,21], minute=0))
--
2.30.2


hardknott build issue

Marek Belisko
 

Hi,

I'm meta-sunxi co-maintainer and in order to add hardknott support to
meta-sunxi I try to build few days ago image from hardknott release
and hitting this issue:

WARNING: core-image-base-1.0-r0 do_rootfs: libglib-2.0-0.postinst
returned 126, marking as unpacked only, configuration required on
target.
WARNING: core-image-base-1.0-r0 do_rootfs: eudev-hwdb.postinst
returned 126, marking as unpacked only, configuration required on
target.
ERROR: core-image-base-1.0-r0 do_rootfs: Postinstall scriptlets of
['libglib-2', 'eudev-hwdb'] have failed. If the intention is to defer
them to first boot,
then please place them into pkg_postinst_ontarget_${PN} ().
Deferring to first boot via 'exit 1' is no longer supported.
Details of the failure are in
/home/builder/build/tmp/work/orange_pi_zero-poky-linux-gnueabi/core-image-base/1.0-r0/temp/log.do_rootfs.
ERROR: Logfile of failure stored in:
/home/builder/build/tmp/work/orange_pi_zero-poky-linux-gnueabi/core-image-base/1.0-r0/temp/log.do_rootfs.8491
ERROR: Task (/home/builder/poky/meta/recipes-core/images/core-image-base.bb:do_rootfs)
failed with exit code '1'

I'm building core-image-base without any other changes. Ideas?

Thanks and BR,

marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Re: Yocto Technical Team Minutes, Engineering Sync, for April 20, 2021

Nicolas Dechesne
 



On Tue, Apr 20, 2021 at 7:35 PM Trevor Woerner <twoerner@...> wrote:
Yocto Technical Team Minutes, Engineering Sync, for April 20, 2021
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== announcements ==
The upcoming Yocto Project Summit is taking place May 25-26 2021
details: https://www.yoctoproject.org/yocto-project-virtual-summit-2021/
CfP: https://pretalx.com/yocto-project-summit-2021/cfp
registration: https://www.cvent.com/d/yjq4dr/4W?ct=868bfddd-ca91-46bb-aaa5-62d2b61b2501

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Armin Kuster, Steve Sakoman, Peter
Kjellerstedt, Alexandre Belloni, Michael Opdenacker, Scott Murray, Jon
Mason, Michael Halstead, Richard Purdie, Bruce Ashfield, Ross Burton, Randy
MacLeod, Saul Wold, Tim Orling, Daiane Angolini

== notes ==
- 3.3 (hardknott) released!!
- 3.1.7 (dunfell) through QA, pending TSC approval
- YP TSC: 3 seats re-elected, 2 seats up for re-election
- master branch open for 3.4 (honister) and things are starting to merge
- new command proposed: bitbake-getvar
- AB issues: 59 (going up)

== general ==
RP: the re-election for OE TSC is coming up in August, but the re-election for
    the YP TSC is in May. a call for candidates will be going out soon
TrevorW: do we want to align the voting with the conference?
RP: probably not


MichaelO: is there a 3.3 celebration?
RP: usually we do it at the conferences, but we’ll have to do it at the
    virtual one this year
MichaelO: i didn’t see anything on lwn
RP: we don’t have a mechanism for this
MichaelO: there are usually release notes
RP: yocto-announce mailing list
TrevorW: release notes?
RP: yes, PaulE put together some notes
TrevorW: is someone putting a release note together?
MichaelO: okay, i’ll put it together and email internally first
RP: advocacy is less that it was, if people can think of places to
    help/advertise that would be great. sometime i publish something in the LF
    newsletter

I think we should indeed improve that a bit. As far as I know, the only place for the release notes is the 'email' sent to yocto-announce, which includes the content from this file:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.3/RELEASENOTES

At the very least we should probably produce (as part of the release process) a similar document that we publish on the website site. That would help us share the news on various social media. We either need to reformat the content for the web , e.g. more verbose, or at least copy/paste into an html page. 
We also recently discussed moving the release notes to docs.yp.org, so perhaps that could be enough to publish it here. The point is it's simpler to share a link on twitter, linkedin, .. that this 'raw/text' file.
 


RP: bitbake-getvar, instead of “bitbake -e | grep”. saves people some
    keystrokes
RP: uses tinfoil, acts as a very good, very small example of how to write a
    small tinfoil tool (e.g. c larson’s bb tool). maybe a way of expanding
    this infrastructure to make it easier to add tools in the future, perhaps
    expandable in layers itself
RP: also perhaps could be used for layer and config setup (e.g. kas,
    combo-layer)
AlexB: sounds great! i often show students “bitbake -e | grep” and
    they’re often surprised and happy to see it
ScottM: +1
RP: it’s in master-next. there are probably a lot of tutorials that will
    need updating after this :-) and there are places in selftest where we do
    “bitbake -e | grep” (it runs it once then builds a dictionary of the
    results to avoid having to run it multiple times throughout the test run)
RossB: it’s similar to bbvars
RP: i’d like to keep it simple, single variable, i don’t want to get too
    much scope creep which makes it more complicated. not meant to solve all
    problems, just solve one elegantly. if we add something to take multiple
    vars then we’d have to return JSON (?) or something else that would be
    machine-parsable
RP: i think a separate command to do multiple vars would be best


PeterK: don't forget to move poky-conf back to master
RP: ah, thanks


Saul: CentOS 8 issues, grrr
RP: i haven’t looked into it
Saul: i think qemu is dying and qmp is trying to read the linux socket and
    getting nothing. maybe i could take out the centos builder for a while
RP: sounds reasonable. if you want to pull one builder out to work on it, that
    would be fine
Saul: i’ll talk to MichaelH about it


Saul: any cmake experts out there?
<crickets>
Saul: i have a nasty cmake + python issue wrt ceph: it doesn’t find the
    core gcc libraries, sysroot being set to /not/exist. i think there’s an
    environment passing issue between cmake and the python
RP: that /not/exist is something *we* hardcode into the compiler to make sure
    sysroot gets set
Bruce: have a look at what we did in libvirt recently. we had a similar issue
    with meson whereby it couldn’t find getent from libc. we had to create a
    patch. meson+cmake couldn’t find getent from libc
RossB: i’ll take a look at your patch Bruce, meson acts strange in some
    ways, but sometimes there’s a way to straighten it out


ScottM: Steve: 3.1.7 this week?
SteveS: up to TSC to approve it
RP: it’s through QA, QA didn’t flag any issues (there was one failure but
    it succeeded on a subsequent build). the TSC meeting is later today, so if
    they approve it’ll be out by tomorrow


Randy: latency monitoring. turned down from 10 to 6 seconds, tuned timeout
    from 5 to 15 seconds. new column in AB console to link to this new data.
    generates graphs of “time to dd 100 kb periodically” to hopefully help
    correlate failures with load. we usually see 3-5 seconds but sometimes 50s
    for unexplained reasons
RP: that’s very interesting. but we still don’t know what the system is
    doing at those times when we see the 20. it’s one thing to know it’s
    happening, it’s another to know why. i’ve noticed that webkit builds
    add a lot of load, also compression adds a lot of load (xz)
Randy: behind on the rust things since i’ve been working on this


RP: speaking of languages, Go also worries me. Go has 2 issues: the fetcher
    is messy and builds are not reproducible. are there any Go experts in our
    community who can help?
TimO: Bruce and I have been struggling over a bunch of things, but it’s not
    fun
Bruce: working on something; i’m currently up to 37 fetches, but it’s not
    just fetching but also a layout issue. if you fetch something to “c/a”
    but Go expects to find it at “a” then it won’t use it
Randy: someone wrote a cargo module for Rust to do something similar (i.e. a
    translation between Rust and bitbake), would that pattern be useful here?
Bruce: probably, hard to know at what point we need to make deep changes vs
    patches on the surface. the “make” infrastructure doesn’t help, too
    many hard-coded paths and options in the Go  “make” files
RP: and that’s only ½ the problem (still have build reproducibility issues)
Bruce: Khem can bump the Go version, but then we need to chase after all these
    fixes


Randy: suricata?
Armin: yes, those are in meta-security now, donated by ARM
Randy: did you use a cargo build
Armin: it was a couple things, had to start with one but then switch over
    partway


TrevorW: is there any update on the “layout of where patches go” work?
RP: you mean “work directory” vs “source directory”?
RP: pretty invasive things, put it aside for now. a change like this will end
    up causing lots of follow-on issues for weeks to come. the cleanup would
    be nice, don’t know if the cost is worth it and would eat up my time for
    a while. although i agree the time would be best now to do it (start of
    new release). i think this is the second time i’ve tried


RP: parallel make job server (another such example of something I’ve looked
    at and think would be nice, but have had to put aside for the time-being)
RP: the todo list isn’t too bad, but it’s something that fell off to the
    side.
RP: i get the feeling that some of the things Randy is trying to track down
    (load on AB servers) might end up being helped by having a parallel job
    server, but we just don’t know
ScottM: is that branch still around. i’m interested in tinkering with it
RP: ignore the branch, just take the commit.
RP: i had hard-coded the fifo to one place (/tmp) on the machine, which means
    every build on that machine is tied together. is that good or bad?
ScottM: is that something you could see being global for all bitbake on the
    machine
RP: as long as all the builds are being run by the same user. probably need to
    create a separate fifo, give it a relevant name, and place it somewhere
    where each user can access it themselves. maybe i should try it on the AB
    and see what blows up



4141 - 4160 of 57343