<belgianguy>
Is there a way to have the image require disk encryption by default, or would that always involve third party tools when deploying (eg terraform)
kpo has joined #yocto
Xagen has joined #yocto
zelgomer has quit [Ping timeout: 246 seconds]
zelgomer has joined #yocto
Ablu has quit [Ping timeout: 256 seconds]
Ablu has joined #yocto
camus has quit [Ping timeout: 246 seconds]
camus1 has joined #yocto
sakoman has quit [Quit: Leaving.]
camus1 is now known as camus
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
kpo has quit [Ping timeout: 248 seconds]
starblue has quit [Ping timeout: 245 seconds]
starblue has joined #yocto
tlwoerner has quit [Ping timeout: 246 seconds]
tlwoerner has joined #yocto
sakoman has joined #yocto
jclsn has quit [Ping timeout: 245 seconds]
jclsn has joined #yocto
BobPungartnik has joined #yocto
Marian97 has joined #yocto
Marian1 has joined #yocto
<Marian1>
Hi,
<Marian1>
I need some help to enable networking.service and ifupdown on Yocto kirkstone with systemd.
beneth has quit [Read error: Connection reset by peer]
davidinux has quit [Ping timeout: 246 seconds]
davidinux has joined #yocto
pabigot has joined #yocto
Schlumpf has joined #yocto
rfuentess has joined #yocto
<LetoThe2nd>
yo dudX
olani has quit [Ping timeout: 240 seconds]
<alessioigor>
good morning
olani_ has quit [Ping timeout: 245 seconds]
<Schlumpf>
good morning
Kubu_work has joined #yocto
RP has quit [Read error: Connection timed out]
hcg has joined #yocto
hardliner66 has joined #yocto
<hardliner66>
hi. I'm trying to get zig into my yocto build, but I wanted to use the compiled binary version instead of building from source. I created a bb file with devtool, but when I'm depending on it, it says it can't find the zig binary. I used the meta-zig layer as a base, but changed the actual bb to my generated one. I put the contents on paste.rs if anyone wants to have a look:
<RP>
michalsieron: you can't do that, it won't work. The output from do_install goes to two places, do_package and do_populate_sysroot
<michalsieron>
yeah. exactly. that's the issue
<RP>
michalsieron: that function is needed for do_package but will break do_populate_sysroot which is why it is used for do_package
<michalsieron>
there are build time paths in the artifacts. more precisely `sysconfig` module has them
<RP>
michalsieron: in the sysroot, probably but they aren't there on target
<RP>
michalsieron: I don't know which paths or what they're being used for. Certainly in the native sysroot, they're probably needed for python to function correctly though
<RP>
to the original question, the bindir functionality will break things if removed
<michalsieron>
RP: let's leave the bindir question. I was just making sure that it is required
<michalsieron>
RP: but going back to the `sysconfig` module. there is this apparmor recipe (https://layers.openembedded.org/layerindex/recipe/60225/), which when I build it, then it reads config flags of python and then compiles its C module with them. and then the package for target contains build time paths in the debug info
<michalsieron>
RP: but also, I don't think those build-time paths in `sysconfig` are required for python3-native to work. what about the situation where you get the artifacts from upstream sstate cache? then you have build-time paths of completely different host machine
pxv03011 has joined #yocto
pxv03011 has quit [Client Quit]
pvogelaar has joined #yocto
<RP>
michalsieron: sstate will relocate them correctly
<RP>
michalsieron: I don't know the answer to the question about specific paths unfortunately
<michalsieron>
> sstate will relocate them correctly
<michalsieron>
RP: what do you mean here?
<dvergatal>
RP: I have seen the build with JPEW fixes and strangely there are erro, which does not occur on my side
ptsneves has joined #yocto
ptsneves1 has joined #yocto
<dvergatal>
errors*
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
ptsneves has quit [Ping timeout: 248 seconds]
ptsneves1 is now known as ptsneves
beneth has joined #yocto
<olani->
adrianf: Well written classes export their task functions as (in your case) cmake_do_compile and module_do_compile. You can call these functions from your own do_compile in the recipe: do_compile() { ; module_do_compile; cmake_do_compile; }
<olani->
adrianf: You will need to do the same for any task function defined in both classes.
ptsneves has quit [Ping timeout: 256 seconds]
ptsneves1 has joined #yocto
ptsneves has joined #yocto
ptsneves1 has quit [Ping timeout: 246 seconds]
<mcfrisk>
hey, is there specific reason why df.py oeqa runtime test has static 5 Mb limit for free space? core-image-minimal will fail that test if IMAGE_FEATURES += "ssh-server-dropbear" is added to the image which is needed to run the test. Fix is to increase core-image-minimal size, but I don't think a static size makes sense. I'd rather configure the free space to be what df.py expects.
<kanavin>
components can, and do place time into 32 bits internally. Sometimes it's in the core structure definition, like in tcl :(
<kanavin>
no amount of glibc trickery is going to help with that kind of short sightedness
<RP>
kanavin: looks like some good work in the branch!
<RP>
kanavin: unfortunately that isn't a surprise, 32 bit time was always going to be a challenge :/
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<kanavin>
RP: yes. it also doesn't help that classical C is ambiguous about how many bits are in integer types.
<kanavin>
modern languages learned from this, and say specifically: int32, int64 etc.
<RP>
kanavin: a good idea at the time :)
<dvergatal>
kanavin: you can always use stdint.h for that ;p
<kanavin>
dvergatal, the problem is not learning at runtime how many bits there are, the problem is that long is 32 bit on one machine and 64 bit on another
<RP>
kanavin: not sure what to do with the long list of backports in master-next for lttng-tools and y2038
<RP>
kanavin: upstream won't release master until end of the year
<kanavin>
RP: that depends on whether you'd like to enable ptest on x86 soon, later or not anytime soon. I can ignore those failures in local testing until there's an upstream release.
<RP>
kanavin: I think we just hacked lttng's flags for now
<RP>
kanavin: upstream were open to the idea of a backport but it is a large chunk of patches
<kanavin>
RP: I am getting lttng ptest fails on x86 (without these patches). I don't think there's any special flag handling - they're getting built with 64 bit time like almost everything else.
<kanavin>
RP: I did however address all strace problems that prevented building it with 64 bit time.
<RP>
kanavin: why isn't the autobuilder seeing lttng failures? I guess because we don't run 32 bit ptests on it?
<kanavin>
RP: no we don't. Something I would like to do, but I don't want to give you stress.
<RP>
Builds are taking too long atm and we're struggling for help with the existing intermittent issues :(
<kanavin>
RP: yes, exactly that
<kanavin>
I saw you fixed one issue from bugzilla that was offered for me, but I can try to take more. It's just difficult to switch context away from y2038, but I'll try!
<kanavin>
I'm kind of on a roll there :-D
<RP>
kanavin: I understand. That other one was "easy" once I found a reproducer for it
<RP>
sometimes it helps for me to work on something not crazy
<dvergatal>
kanavin: what can I say...
rfuentess has joined #yocto
<kanavin>
Presumably whoever wrote that assumed they'll be dead in 2038, or something.
<ptsneves>
When running bitbake with setscene-only, does it stop with exit code !=0 when a needed sstate cache entry is not found?
<ad__>
hi friends. How to set default sh to busybox, from gnu bash ? (hardknott)
<ad__>
i set VIRTUAL-RUNTIME_login_manager = "busybox" but gnu bash is still the default
flom84 has quit [Ping timeout: 245 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Xagen has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
ecdhe has quit [Read error: Connection reset by peer]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<ad__>
i have tried IMAGE_INSTALL_remove = " bash ", bash still there
ecdhe has joined #yocto
<JaMa>
ad__: you would need to replace bash in all the runtime dependencies of all the installed packages (we do that in webOS)
<ad__>
JaMa: i just need to replicate a nbuildroot image, that uses busybox ash. maybe i can just rm bash and add a symlink to ash
<JaMa>
the symlink is automatically created when you enable ASH_IS_BASH in busybox defconfig, but that doesn't prevent gnu bash being pulled into the image by rdeps
<JaMa>
but if you don't mind having bash in image as well, then u-a priority setting might be enough
<ad__>
JaMa: well, yes, i don't mind. How do i set the priority ?
xmn_ has quit [Quit: xmn_]
<yates_work>
is there some way i can make a small contribution to the yocto project that would benefit everyone here who gives of their time graciously?
<ad__>
yates_work: allows to change bash to bb ash :)
<yates_work>
i meant a monetary contribution! :)
<yates_work>
would some help be more valuable than money?
<yates_work>
LetoThe2nd: ^^^^
alessioigor has quit [Ping timeout: 245 seconds]
<LetoThe2nd>
yates_work: there is a donation path through LFX, but generally work contributions are far more valueable than just money to us. There are beginner-marked bugs in bugzilla for example. Or if you, respectively your employer are serious about things, then working with them together to join as Members.
<yates_work>
i am finding that, after configuring for qemuarm and building core-image-sato (which works beautifully), if i subsequently "bitbake qt5ledscreen", the resulting binary is NOT placed in the main core-image-sato rpm subfolder, which appears to be work/qemuarm-poky-linux-gnueabi/core-image-sato/1.0-r0/oe-rootfs-repo/rpm/, and neither is the associated repomd.xml updated.
<yates_work>
how do i make that happen?
<yates_work>
i see the qtlledscreen output binary in deploy, but it never makes it over to the final packaging folder
flom84 has quit [Ping timeout: 245 seconds]
olani- has quit [Ping timeout: 256 seconds]
olani- has joined #yocto
roussinm has quit [Quit: WeeChat 3.8]
<ptsneves>
yates_work: core-image-sato is an image recipe while qt5ledscreen appears to be an regular recipe. When you build qt5ledscreen you are just building the recipe and are not building the image. That is why the image's workspace does not get updated. Anyway if you only want qt5ledscreen rpm you can find it in the deploy directory after building that recipe
roussinm has joined #yocto
<roussinm>
I have intentionally set REQUIRED_VERSION_gcc to a wrong version, and I don't get any warning/errors, if there is only version of the recipe does that work? My ultimate goal is to be able to fetch gcc version from another recipe, and tried to used REQUIRED_VERSION_gcc, but that doesn't seem to work. How can I get the version of another recipe in a recipe?
LocutusOfBorg has quit [Ping timeout: 245 seconds]
<ptsneves>
roussinm: gcc is a collection of recipes which are not exactly called gcc. You would either need to set preferred version or even provider for the default gcc recipe collection or inspect the toolchain settings. I do not know it by heart for example, but depending on what you want to do you may need to understand better how Yocto configures the toolchain.
<roussinm>
ptsneves: From this inc file: poky/meta/conf/distro/include/tcmode-default.inc it looks like a bunch of PREFERRED_VERSION_gcc-... are already present.
TheStig has quit [Remote host closed the connection]
flom84 has joined #yocto
<ptsneves>
roussinm: Yep that is the file. So to give it a try modify it to point to your versions. Then you can just create a new tcmode conf
rfuentess has quit [Remote host closed the connection]
jtoomey has joined #yocto
florian_kc has quit [Ping timeout: 248 seconds]
<roussinm>
ptsneves: ptsneves would there be a way instead to expand the variable GCCVERSION, because since it's written like "12.%" I don't get the real version. I need to create a symlink in a cross-canadian recipe where the version of gcc is a directory.
Tyaku has joined #yocto
leon-anavi has quit [Quit: Leaving]
florian has quit [Quit: Ex-Chat]
<Tyaku>
Hi, I have a recipe for the kernel with a bbappend that add various fragments files for various things. Today I would like to create a fragment : "CONFIG_PANIC_TIMEOUT=5" *but* i only want that fragment in the build if I build with my "main" image. On my yocto project I have two image for exemple: "main" and "main-dev". The main-dev image just add package that are used for the dev (ssh server, rsyslog,
<Tyaku>
gdbserver etc). I want the fragment active in main image but not in dev image.
<Tyaku>
In the dev image when a kernel panic happens i want it to block infinitely
<Tyaku>
In the main image (production image), when a kernel panic happens i want it to reboot
<Tyaku>
Did someone know how to condition a SRC_URI:append in a recipe to the *image name* ?
<Tyaku>
I know how to condition a SRC_URI:append to a *machine* but not to an *image*
<Tyaku>
or to override kernel configuration in an *image* (like adding a fragment)
belgianguy has joined #yocto
<ptsneves>
roussinm: I do not know. This is not something I have done in some years. Maybe somebody else can help you .
<ptsneves>
Tyaku: There is no way to have an image propagate information to another recipe. An image is essentially just a recipe, so that is just how recipes work: They do not affect eachother. If you want to do something similar I suggest using an inc file and have the 2 recipe variants use the .inc file and an extra SRC_URI entry where relevant. Then in your image you add the relevant package
valdemaras has joined #yocto
Tyaku has quit [Quit: Lost terminal]
michalsieron has quit [Ping timeout: 246 seconds]
alessioigor has quit [Quit: alessioigor]
<Saur>
RP: Regarding the removal of ${SRCPV}. After your latest changes, I believe you have addressed all my original concerns.
<Saur>
RP: I like the use of the `+` character to indicate when the expansion is needed.
<Saur>
RP: However, see my response to the architecture list as it contains a new problem I discovered.
florian_kc has joined #yocto
geoffhp has joined #yocto
kpo_ has joined #yocto
kpo has quit [Ping timeout: 246 seconds]
kpo has joined #yocto
kpo_ has quit [Ping timeout: 245 seconds]
<yates_work>
ptsneves: of course. now i see. thanks.
d61 has joined #yocto
<yates_work>
if i wanted to "extend" core-image-sato into my own custom image, would i have to just copy the .bb and modify to suit, or is there some way to extend it?
valdemaras has quit [Quit: valdemaras]
<ptsneves>
yates_work: This is a very basic question and suggests you should spend some time familiarizing with the Yocto eco system. It will save you time. I suggest you start by bbappend
<yates_work>
ptsneves: "I suggest you start by bbappend" would have been sufficient sans the judgment.
<yates_work>
and, unfortunately, "spending some time" would mean probably weeks of reading documentation. the good thing about yocto is it has lots of documentation. the bad thing about yocto is it has lots of documentation.
<yates_work>
..and i have already been down the yocto road - it's just been awhile.
<yates_work>
..and i'm getting old and forgetful..
kpo has quit [Quit: Konversation terminated!]
<yates_work>
i will say the guy who wrote the variables glossary needs an award..
<yates_work>
guy/person
<ptsneves>
It is unfortunate you find it judgemental. Good luck
<belgianguy>
Hi all, is secure boot possible on an ARM64 system built using Yocto? Google gives conflicting information, and it seems it only was repaired on Debian (and I don't know how to check which base distro Yocto picked for dragonboard-410c (meta-qcom))
<belgianguy>
repaired recently*
<fray>
yes it is possible, depends on the board, cpu and configuration. For that particular board, I don't know what nay be required or if works out of the box
<Saur>
RP: Btw, after libera.chat pulled the plug on the Matrix bridge two weeks ago, I do not have access to the chat during weekends and off-hours so do not expect any chat replies until Monday.
<jonmason>
is anyone seeing libtraceevent issues when compiling perf?
belgianguy has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 252 seconds]
flom84 has joined #yocto
flom84 has quit [Ping timeout: 246 seconds]
amitk_ has joined #yocto
florian_kc has joined #yocto
d61 has quit [Quit: WeeChat 3.8]
florian_kc has quit [Ping timeout: 245 seconds]
florian_kc has joined #yocto
flom84 has joined #yocto
flom__84__ has joined #yocto
flom84 has quit [Ping timeout: 246 seconds]
flom__84__ has quit [Quit: Leaving]
flom84 has joined #yocto
dash_hope has joined #yocto
pabigot has quit [Ping timeout: 246 seconds]
amitk_ has quit [Ping timeout: 258 seconds]
pabigot has joined #yocto
flom84 has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
lexano has joined #yocto
dash_hope has quit [Ping timeout: 246 seconds]
roussinm has quit [Quit: WeeChat 3.8]
belgianguy has joined #yocto
alejandrohs has quit [Read error: Connection reset by peer]
alejandrohs has joined #yocto
florian_kc has quit [Ping timeout: 245 seconds]
<geoffhp>
yates_work: Another way to extend core-image-sato.bb besides using a .bbappend file is to start a 'my-image.bb' and put 'require core-image-sato.bb' . That way you can have a different name for your image. Also, there is core-image.bbclass you can extend in your 'my-image.bb' recipe with 'inherit core-image'
<geoffhp>
yates_work: Another way to extend core-image-sato.bb besides using a .bbappend file is to start a 'my-image.bb' and put 'require core-image-sato.bb' . That way you can have a different name for your image. Also, there is core-image.bbclass you can inherit in your 'my-image.bb' recipe with 'inherit core-image'
sakoman has quit [Ping timeout: 246 seconds]
DvorkinDmitry has joined #yocto
Kubu_work has quit [Quit: Leaving.]
Marian71 has joined #yocto
<Marian71>
Hi,
<Marian71>
I'm trying to runqemu a genericx86-64 wic core-image-minimal "MACHINE="genericx86-64" runqemu custom-test-image wic nographic slirp"