We do run world on every master tip, so yes it should succeed. It doesn't seem to be related to disabling introspection, but you might want to retry with it enabled to be sure.
If target rust continues to fail no matter what you try, then 'bitbake -k world' will continue building what it can when fails occur. Alex On Thu, 5 Jan 2023 at 15:13, Petr Kubizňák <[email protected]> wrote: > > Is the `bitbake world` command guaranteed to succeed for every commit in the > repository? In my case, I end up with failures even with _default_ setup. My > point is whether this has to be an issue on my machine (e.g. native tools?), > or I should just try a different commit. > > > Build Configuration: > BB_VERSION = "2.2.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "universal" > TARGET_SYS = "x86_64-poky-linux" > MACHINE = "qemux86-64" > DISTRO = "poky" > DISTRO_VERSION = "4.1" > TUNE_FEATURES = "m64 core2" > TARGET_FPU = "" > meta > meta-poky > meta-yocto-bsp = "HEAD:2c6f0b9228b47459dd1b67d578792cd017006128" > ... > ERROR: rust-1.66.0-r0 do_compile: > ExecutionError('/home/kubiznak/projects/poky/builds/test-gi/tmp/work/core2-64-poky-linux/rust/1.66.0-r0/temp/run.do_compile.1080378', > 1, None, None) > ERROR: Logfile of failure stored in: > /home/kubiznak/projects/poky/builds/test-gi/tmp/work/core2-64-poky-linux/rust/1.66.0-r0/temp/log.do_compile.1080378 > NOTE: recipe rust-1.66.0-r0: task do_compile: Failed > ERROR: Task > (/home/kubiznak/projects/poky/meta/recipes-devtools/rust/rust_1.66.0.bb:do_compile) > failed with exit code '1' > > The first error in rust log: > > error: > /home/kubiznak/projects/poky/builds/test-gi/tmp/work/core2-64-poky-linux/rust/1.66.0-r0/rustc-1.66.0-src/build/x86_64-unknown-linux-gnu/stage1-rustc/release/deps/libunic_langid_macros_impl-09018f99e8b09dcb.so: > undefined symbol: _Ungind_Resume > --> > /home/kubiznak/projects/poky/builds/test-gi/tmp/work/core2-64-poky-linux/rust/1.66.0-r0/rustc-1.66.0-src/vendor/unic-langid-macros/src/lib.rs:5:9 > | > 5 | pub use unic_langid_macros_impl::langid; > | ^^^^^^^^^^^^^^^^^^^^^^^ > > Full logs attached. > > > Petr > > ________________________________ > From: Alexander Kanavin <[email protected]> > Sent: Wednesday, January 4, 2023 1:36:27 PM > To: Petr Kubizňák - 2N > Cc: [email protected] > Subject: Re: [OE-core][PATCH 1/2] gobject-introspection: check for > GI_DATA_ENABLED > > On Wed, 4 Jan 2023 at 13:24, Petr Kubizňák <[email protected]> wrote: > > Yes, that's exactly the reason. I'm particularly concerned about dependency > > on glib, but other dependencies are unnecessary, too. > > > > > > This change was sufficient to remove the dependency from the target. I am > > not aware of potential consequences of removing the -native dependencies, > > but if you think it should also be done, I'm happy to update the patch. > > Please let me know. > > I'd suggest that you remove all three, then set up a plain poky master > build with gobject-introspection-data disabled, and issue bitbake > world. > > Component upstreams generally only test the gi-enabled configuration, > so this may reveal incorrect upstream logic when g-i is disabled. > > Alex > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#175530): https://lists.openembedded.org/g/openembedded-core/message/175530 Mute This Topic: https://lists.openembedded.org/mt/96048399/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
