kanavin_ has quit [Remote host closed the connection]
<ptsneves>
Do i understand right that the code in https://git.yoctoproject.org/poky/tree/meta/classes/useradd.bbclass#n125 is redundant because the useradd_sysroot only runs for target recipes and the class sets DEPENDS:append:class-target = " base-files shadow-native shadow-sysroot shadow base-passwd". Is there any case i am missing where the DEPENDS are not honored, like in an image recipe?
kanavin has joined #yocto
zpfvo has quit [Ping timeout: 255 seconds]
zpfvo has joined #yocto
Chaser has joined #yocto
<rburton>
PhoenixMage: set the password to a string you assign using python's secret library
<PhoenixMage>
rburton: Cheers, I'll look into it
<qschulz>
tlwoerner: thanks for the merge of rk3588 support back to kirkstone <3
<PhoenixMage>
Damn, that reminds me I need to resend my patch for the rk3568 stuff
<PhoenixMage>
tlwoerner: Did you get a chance to test the ethernet with the yocto-dev kernel in master?
<PhoenixMage>
Pretty sure the ethernet wont work in the kirkstone unless you run a custom kernel
<PhoenixMage>
I havent tested master, all my stuff is kirkstone
amitk_ has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
tnovotny has joined #yocto
zpfvo has joined #yocto
florian has joined #yocto
tnovotny_ has joined #yocto
tnovotny has quit [Ping timeout: 252 seconds]
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 255 seconds]
zpfvo has joined #yocto
amitk_ has quit [Ping timeout: 255 seconds]
zelgomer has quit [Remote host closed the connection]
zelgomer has joined #yocto
mvlad has joined #yocto
otavio has quit [Remote host closed the connection]
otavio has joined #yocto
<Rich_1234>
I have a core-image-weston with Chromium. I need to adjust my clock time to access certain pages. I don't have hwclock or timedatectl. Easiest solution? Does Busybox provide things for time adjustment?
frieder has quit [Ping timeout: 272 seconds]
prabhakarlad has quit [Quit: Client closed]
<landgraf>
Rich_1234: data?
<landgraf>
Rich_1234: date ?
<PhoenixMage>
Busybox has a rudementary hwclock I think
frieder has joined #yocto
frieder has quit [Ping timeout: 245 seconds]
rob_w has quit [Remote host closed the connection]
<kanavin>
rburton, hopefully we can neatly sidestep this by building glib-native as the 'first step' instead of building glib twice
<rburton>
i expect that won't be sufficient but you never know
<rburton>
shout if you look at it because its on my todo list but i doubt i'll do that today
prabhakarlad has joined #yocto
<Rich_1234>
landgraf, yeah date is set to march 9th
<Rich_1234>
the actual time I think is fine
<landgraf>
Rich_1234: date -s 'Mon Oct 16 15:00:33'
<Rich_1234>
landgraf I will give that a go, cheers
frieder has joined #yocto
tgamblin_ is now known as tgamblin
vladest has joined #yocto
tnovotny_ has quit [Quit: Leaving]
varjag has quit [Quit: ERC (IRC client for Emacs 27.1)]
bhstalel has joined #yocto
<Rich_1234>
landgraf date did work thanks, just had to do date -s '2023-10-16 ab:xx:xx'
frieder has quit [Ping timeout: 240 seconds]
linfax_ has quit [Ping timeout: 240 seconds]
<danlor>
Hi! Has anyone had issues when installing ca-certificates-java into the image? The update-ca-certificates java hook is failing when executing the postinstall (ca-certificates postinstall is being executed before ca-certificates-java). I'm on Kirkstone, but ca-certificates and ca-certificates-java don't seem to have changed since. I've not been able
<danlor>
to find anything related to this.
leon-anavi has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
florian has quit [Ping timeout: 252 seconds]
frieder has joined #yocto
goliath has quit [Quit: SIGSEGV]
frieder has quit [Ping timeout: 272 seconds]
rfuentess has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<jclsn>
qschulz: Thx, will have a look
<jclsn>
I already sent a request, but I think I forgot to sign off the commit
frieder has joined #yocto
prabhakarlad has quit [Quit: Client closed]
frieder has quit [Remote host closed the connection]
xmn has joined #yocto
mbulut has quit [Ping timeout: 255 seconds]
danlor has quit [Quit: Client closed]
leon-anavi has quit [Quit: Leaving]
danlor has joined #yocto
ptsneves has quit [Ping timeout: 255 seconds]
<danlor>
Okey, it only fails when PACKAGE_CLASSES = "package_deb"
florian_kc has quit [Quit: Ex-Chat]
zpfvo has quit [Ping timeout: 258 seconds]
Chocky has joined #yocto
<Chocky>
Greetings!
<Chocky>
I have a custom fetch setup for a recipe in kirkstone. During the unpack phase, but not in the actual unpack step itself, the contents of my src directory get erased. Trying to track down the code that does this. What am I missing?
<RP>
Chocky: do_unpack[cleandirs] = "" in your recipe would likely avoid it :)
<Chocky>
indeed.
<Chocky>
I did OpenWrt for many many years; Yocto still has a lot of weird corners for me.
Chaser has quit [Quit: Chaser]
danlor has joined #yocto
<bhstalel>
Chocky Yocto will be your best friend.
* Chocky
blames fullstop
<Chocky>
well, I doubt that, but I owner many sized hammers.
zpfvo has joined #yocto
danlor has quit [Client Quit]
<RP>
Chocky: I am a little curious on where you notice the big differences and if there are things we should be doing differently
<Chocky>
Yeah, I don't know. I don't want to start a philosophy way or anything, and in the end they, and Linux are just tools. A boss of my mine many decades ago was Phil Blundell, who founded OpenEmbedded stuff my history with this stuff goes back quite a ways.
bhstalel has quit [Quit: Client closed]
<Chocky>
The biggest obvious difference between OpenWrt and Yocto is that the former uses a common staging area, but Yocto puts all the build stuff in a per-recipe build directory. There's pros and cons to each.
<RP>
Chocky: Right, I'm not trying to get into the philosophy discussion! :) I do sometimes wonder if we can make things easier in places though so I try and have an open mind. Clearing do_unpack before we start does conceptually make sense as you then start from empty each time
<Chocky>
What I can certainly say is that for my co-workers coming to Yocto from non-Linux backgrounds, it's extraordinarily difficult to track down issues. That's partly due to the nature of how cross compiling has to work. I don't have any good answers to that.
<RP>
As you say, there are pros and cons to recipe vs common staging areas
<Chocky>
I think OpenWrt is fantastic, but it's also understaffed, especially security and things.
<RP>
Chocky: I did work with pb_ and miss some of his input...
<RP>
and yes, cross compiling is a pain
<Chocky>
You may also remember Wookey; someone else I used to work a lot with.
<RP>
Chocky: yes, rburton works with him
<Chocky>
"Wookey, only one name, and it's the second one"
<rburton>
amusingly, the orgchart claims that wookey is known as '.'
<RP>
Chocky: there is only one wookey :)
<Chocky>
I'd like to see a menuconfig in Yocto (beyond the Linux kernel), but perhaps that's impractical - one of the downsides in OpenWrt is that if you make targets for multiple platforms, they really all need to be identical in term of packages.
bhstalel has joined #yocto
<bhstalel>
Why RECIPE_SYSROOT is not in variables documentation ??
<rburton>
bhstalel: patches welcome
<Chocky>
I'm also seeing Zephyr, which is of course not Linux, but it's taking a lot of cues from Linux build systems.
<rburton>
(because variables get added without remembering to update the docs)
<bhstalel>
I am thinking to add it, of course, but I thought it was intentional or something
<rburton>
nope
zpfvo has quit [Quit: Leaving.]
<RP>
Chocky: there are layers to let you build zephyr with YP
<Chocky>
I guess you can build anything with anything if you try hard enough. I certainly have at times
<RP>
Chocky: whilst we primarily do linux you can build firmware, rt systems and all sorts. It is just code...
<bhstalel>
Help me with this, when I send patches and some reviews are done and I need to change something, do I need always to reset the commit and recreate the patch again ?
<bhstalel>
Is there a way to tell git to apply the new commit to the latest commit as well and then recreate the patch ?
<rburton>
look up git commit --amend
<rburton>
or rebase
<rburton>
personally i'll have a branch in progress with commits like "do something", "fix", "arghghhg", "OK I HATE COMPUTERS" but when it works i do an interactive rebase and squash/reword the commits to hide the rage
<bhstalel>
The issue is, I sent a patch, then I worked on something else, then modifications are needed in old commit,
<Chocky>
RP: Yeah, I know. Although sometimes could != should.
<rburton>
bhstalel: feature branches and rebasing. one branch per "feature".
<bhstalel>
So, I create a branch for each, let's say, patch that I intend to commit
<rburton>
well, feature, not patch. if that feature is one patch the fine, but it might be a series of related patches
<bhstalel>
Yes, that's what I meant, that will do it
zenstoic has joined #yocto
<Chocky>
One other flaw with OpenWrt is that whilst it's possible to add files to the final image, that you have staged externally, it's not possible to remove files unless you hack in some post-processing or something.
PhoenixMage has quit [Remote host closed the connection]
Vonter has quit [Ping timeout: 258 seconds]
Vonter has joined #yocto
alimon has quit [Remote host closed the connection]
alimon has joined #yocto
brrm has quit [Ping timeout: 240 seconds]
brrm has joined #yocto
florian has joined #yocto
Minvera has joined #yocto
Guest67 has joined #yocto
<Guest67>
hi all.. there was a switch for bitbake that lists the provider for virtual/kernel. I can't seem to remember it and can't find it onine. Just wondering if anyone else remembers
<Guest67>
thanks thats a totally new command I didnt know about
bhstalel has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
<sudip>
I am trying to upgrade rpm, with the new version its now using cmake and I can see the configure step is failing to find libm.so. I checked the current v4.18.1 and could not find libm.so in recipe-sysroot-native. is the current rpm build using libm from the host ?
Haxxa has joined #yocto
<sudip>
missed saying rpm-native is failing.
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
goliath has joined #yocto
prabhakarlad has joined #yocto
<sudip>
The -lm is being mentioned by lua.pc and that also says "libdir=${pcfiledir}/../../../usr/lib" which is "recipe-sysroot-native/usr/lib/" so libm should be here.
<khem>
sudip: which version are you upgrading to.
<sudip>
4.19.0
<sudip>
but my confusion is with the build of the current version
<khem>
it needs it from uninative I guess
sakman has joined #yocto
<sudip>
but then shouldn't the path be mentioned in LD_FLAGS ?
<sudip>
only reference to uninative I can see is with "dynamic-linker"
<sudip>
unless "dynamic-linker" knows the path already.