otavio has quit [Remote host closed the connection]
shanedora has joined #yocto
<shanedora>
Hi ~ I would like to print out some of these environment variables in yocto that is used by bitbake. There's so many of these variables and apparently they can mean different things based on the context of when they're being build (e.g. per recipe). So lets say I'm building a recipe I created via `bitbake create-layer foo` and I want to print some
<shanedora>
of the various variables that are used by a recipe in that layer called `foo`. How do I do that? For example, do I write a `printf` kind of statement somewhere in the recipe? Is there a command I can use kind of like printing env variables in my bash terminal like `echo $PATH`? I'm very new here so I did try typing `bitbake -h` and I see a option
<shanedora>
called `-e`. Not quite sure how to use it though. Some googling mentioning something like `bitbake -e foo | grep ^WORKDIR=`. Is that how I do this? Why do I need to put the carrot sign and the equals sign in there?
KhazAkar has quit [Quit: Connection closed for inactivity]
shanedora has quit [Quit: Client closed]
shanedora has joined #yocto
shanedora has quit [Quit: Client closed]
shanedora has joined #yocto
florian has quit [Ping timeout: 276 seconds]
lexano has quit [Ping timeout: 255 seconds]
shanedora has quit [Quit: Client closed]
KhazAkar has joined #yocto
ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
starblue has quit [Ping timeout: 255 seconds]
starblue has joined #yocto
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #yocto
Guest46 has joined #yocto
Guest46 has quit [Client Quit]
Dracos-Carazza has joined #yocto
sakman has quit [Ping timeout: 256 seconds]
KhazAkar has quit [Quit: Connection closed for inactivity]
sakman has joined #yocto
taruu has joined #yocto
Dracos-Carazza_ has joined #yocto
Dracos-Carazza has quit [Ping timeout: 256 seconds]
KhazAkar has joined #yocto
Chaser has joined #yocto
jmd has joined #yocto
zpfvo has joined #yocto
linfax has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
albrod has joined #yocto
zpfvo has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
Kubu_work has joined #yocto
alessioigor has joined #yocto
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
albrod has quit [Ping timeout: 250 seconds]
Chaser has quit [Quit: Chaser]
adrian_s has joined #yocto
GNUmoon has quit [Remote host closed the connection]
GNUmoon has joined #yocto
Daanct12 has joined #yocto
alperak has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<LetoThe2nd>
mckoan: hey yo
<mckoan>
LetoThe2nd: hi
mvlad has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
olani- has joined #yocto
olani_ has joined #yocto
Vonter has quit [Ping timeout: 256 seconds]
olani- has left #yocto [#yocto]
Vonter has joined #yocto
olani has left #yocto [Using Circe, the loveliest of all IRC clients]
olani_ has left #yocto [#yocto]
Dartmoness has joined #yocto
olani has joined #yocto
dvergatal has quit [Ping timeout: 256 seconds]
goliath has joined #yocto
dvergatal has joined #yocto
speeder has joined #yocto
zhmylove has joined #yocto
dvergatal has quit [Ping timeout: 245 seconds]
dvergatal has joined #yocto
thaemmerle has joined #yocto
thaemmerle has quit [Quit: Client closed]
alperak has quit [Quit: Client closed]
thaemmerle has joined #yocto
alperak has joined #yocto
dkl has quit [Quit: %quit%]
thaemmerle has quit [Client Quit]
dkl has joined #yocto
Dracos-Carazza_ is now known as Dracos-Carazza
Saur_Home has quit [Quit: Client closed]
Saur_Home has joined #yocto
prabhakarlad has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
starblue has quit [Ping timeout: 264 seconds]
starblue has joined #yocto
ptsneves has joined #yocto
ptsneves has quit [Client Quit]
ptsneves has joined #yocto
tuxinator has joined #yocto
leon-anavi has joined #yocto
ptsneves has quit [Quit: ptsneves]
ptsneves has joined #yocto
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #yocto
prabhakarlad has quit [Client Quit]
Saur_Home has quit [Quit: Ping timeout (120 seconds)]
ptsneves1 has joined #yocto
ptsneves has quit [Ping timeout: 252 seconds]
ptsneves1 is now known as ptsneves
prabhakarlad has joined #yocto
<kanavin>
more bad-ish news with the new rpm 4.19. It has split crypto handling into an external library implemented in guess which language.
tuxinator has quit [Quit: Konversation terminated!]
ptsneves1 has joined #yocto
ptsneves has quit [Ping timeout: 256 seconds]
<sudip>
rpm-sequoia -> rust
<sudip>
but you can add -DWITH_INTERNAL_OPENPGP=ON and then it will use "the deprecated internal parser"
ptsneves has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
<kanavin>
I know, but that would just delay the inevitable
* sudip
started looking into rpm upgrade but ran into multiple problems and now waits to see how kanavin does it
<kanavin>
we might as well just do the switchover now
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<sudip>
yeah, thats true, its either now or in next few release
<kanavin>
do you happen to have a sequoia recipe that I could cherry-pick?
<sudip>
no, I was trying with the internal one
ptsneves1 has quit [Ping timeout: 260 seconds]
<sudip>
but I had a problem with the native build and had to add a patch for cmake.bbclass
<kanavin>
I didn't get there yet, just reached the point where it's asking for this sequoia thingy
<sudip>
I can forward you my half finished patch, didn't get time to complete due to $dayjob
<kanavin>
if you can just publish the work on git somewhere that'd be ok too
<sudip>
so this was the native build problem:
<sudip>
Oct 16 20:15:38 <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 ?
<sudip>
Oct 16 20:38:16 <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.
lexano has joined #yocto
alperak has quit [Quit: Client closed]
<rburton>
libm is part of glibc so yes it uses the hosts libm
<rburton>
we don't build a glibc-native
<sudip>
rburton: yes, that part is done, I was in the next problem and then did not get time
<speeder>
poky by default doesn't have dmidecode installed?
speeder_ has quit [Ping timeout: 252 seconds]
<mckoan>
timeout :-D
<mckoan>
dmidecode is not in Poky, it is provided by meta-oe-image.bb -> packagegroup-meta-oe
zpfvo has quit [Ping timeout: 264 seconds]
speeder_ has joined #yocto
<rburton>
dmidecode is in core
speeder has quit [Ping timeout: 240 seconds]
<rburton>
speeder: its not in any of the reference images, no. you can easily add it. the entire point is that you make your own images.
zpfvo has joined #yocto
egueli-AV has joined #yocto
egueli has joined #yocto
egueli has left #yocto [#yocto]
justThanks is now known as justache
speeder__ has joined #yocto
speeder_ has quit [Ping timeout: 260 seconds]
Rich_1234 has quit [Quit: Connection closed]
speeder_ has joined #yocto
speeder__ has quit [Ping timeout: 256 seconds]
speeder__ has joined #yocto
smooge has quit [Quit: I have resigned. I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered! My life is my own.]
speeder_ has quit [Ping timeout: 255 seconds]
sakman_ has joined #yocto
sakman has quit [Ping timeout: 255 seconds]
doobee has joined #yocto
florian_kc has quit [Quit: Ex-Chat]
speeder_ has joined #yocto
<doobee>
How does bitbake do a `sha256sum` over a git repo I specify in my `SRCURI`? I guess I'm only use to running a sha256sum on a file so I have no idea how bitbake does it over a directory. I tried looking up how to do a sha256sum over a directory and came across something like this `find path/to/dir/ -type f -exec sha256sum {} \; | sha256sum` but the
<doobee>
sum didn't match what bitbake is telling me the sum is. So I need alittle help understanding how I can do this manually. I realize bitbake is doing it for me but I want to understand how it's doing it.
speeder__ has quit [Ping timeout: 256 seconds]
florian has quit [Ping timeout: 260 seconds]
zpfvo has quit [Ping timeout: 264 seconds]
zpfvo has joined #yocto
Tyaku_ has quit [Quit: Lost terminal]
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
speeder__ has joined #yocto
zpfvo has quit [Client Quit]
speeder_ has quit [Ping timeout: 256 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<rburton>
doobee: it doesn't?
<rburton>
doobee: where do you think its doing a sha256sum of a git repo?
<rburton>
i'm guessing you mean SRC_URI[sha256sum], that's for eg http: fetches, not git
<rburton>
it sounds like you've got a bad SRC_URI
<rburton>
if you're cloning a git repo over http then the SRC_URI would be git://...;protocol=https so that bitbake knows to "git clone" not "wget" the url
egueli-AV has quit [Read error: Connection reset by peer]
speeder_ has joined #yocto
speeder__ has quit [Ping timeout: 252 seconds]
<doobee>
Oh ok, so I don't need a SRC_URI[sha256sum] variable then if my SRC_URI is something like `SRC_URI = "git://github.com/me/helloworld.git;protocol=https;branch=main"`.
<rburton>
correct
<rburton>
the SRCREV serves the same purpose
<kanavin>
sudip, I need a bit of support in that oe-architecture thread
<doobee>
So if I don't have a source revision then I don't need that either? I kept thinking I need to set it to `SRCREV = "${AUTOREV}"`.
speeder__ has joined #yocto
speeder_ has quit [Ping timeout: 260 seconds]
<rburton>
you definitely do have a srcrev
<rburton>
you have to name what revision is checked out
<rburton>
if you want it to track HEAD of the specified branch then AUTOREV is what you want
<doobee>
Ah I follow you now. Thank you!
<rburton>
but we're fans of reproducibility by default, so encourage a real SHA that you upgrade as needed
<doobee>
If I created a tag or a release on my github for that repo then I would need to specify a SRC_URI[sha256] and also the revisioning in SRCREV, correct?
zhmylove has quit [Remote host closed the connection]
zhmylove has joined #yocto
<doobee>
Is there an example that I can refer to that uses a github repository with all that specified?
mckoan is now known as mckoan|away
Kubu_work has quit [Quit: Leaving.]
florian has joined #yocto
speeder__ has quit [Ping timeout: 255 seconds]
florian has quit [Ping timeout: 256 seconds]
Chaser has joined #yocto
Vonter has quit [Ping timeout: 256 seconds]
florian has joined #yocto
Vonter has joined #yocto
prabhakarlad has joined #yocto
Chaser has quit [Quit: Chaser]
adrian_s has quit [Ping timeout: 256 seconds]
adrian_s has joined #yocto
smooge has joined #yocto
smooge has quit [Client Quit]
smooge has joined #yocto
<rburton>
doobee: you only need to use a checksum if you download a single file, like a tarball
<rburton>
doobee: for examples, oe-core/poky is full of them
mvlad has quit [Remote host closed the connection]
smooge has quit [Quit: I have resigned. I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered! My life is my own.]
jmd has quit [Remote host closed the connection]
smooge has joined #yocto
smooge has quit [Changing host]
smooge has joined #yocto
Xywzel has quit [Ping timeout: 252 seconds]
Xywzel has joined #yocto
zhmylove has quit [Quit: Leaving]
Saur_Home has joined #yocto
Kubu_work has joined #yocto
doobee has quit [Quit: Client closed]
dan73 has joined #yocto
<dan73>
I have a recipe that builds a c program (i guess yocto calls this an app) `my-app` and then installs it to `${bindir}`. I then added `IMAGE_INSTALL:append = " my-app"` and tested via qemu. I can see it getting dropped into `/usr/bin/my-app`. However, when I try to build a raspberrypi image with `IMAGE_INSTALL:append = " my-app"` added to that
<dan73>
`local.conf` (just as I did with qemu) I don't see my app in `/usr/bin/`. What could I be missing?
<dan73>
Well i'm at a lost on what could be going on. I created a build environment for qemu `source src/poky/oe-init-build-env bld-qemuarm`, added my layer `bitbake-layers add-layer <my layer>`. Then I built a qemu image `bitbake core-image-minimal` ensuring that qemu was set as the machine in my `local.conf`. Also ensured that I had `IMAGE_INSTALL:append
<dan73>
= " my-app" specified too. Launched qemu and my app's binary was there in `/usr/bin/` and I could run it and everything.
<dan73>
Now I wanted to do the exact same thing but for my raspberry pi 4. So I created a new environment `source src/poky/oe-init-build-env bld-rpi`, added my layer `bitbake-layers add-layer <my layer>`. Then I ensure that the machine variable was set appropriately and that `IMAGE_INSTALL:append = " my-app"` was specified. Then I build the image `bitbake
<dan73>
rpi-test-image`. Flashed the image to my sd card and power up the board. Everything booted fine but when I go into `/usr/bin/` I don't see my app. So it's like it worked for qemu but didn't work for my rpi.
<dan73>
hmm ... well ... I can see it there in the rootfs ...
<dan73>
```
<dan73>
1.0-r0/rootfs/usr/bin
<dan73>
☕ ❯ pwd
<dan73>
1.0-r0/rootfs/usr/bin took 14s
<dan73>
☕ ❯ ll | grep main
<dan73>
-rwxr-xr-x 1 shane shane 67552 Mar 9 2018 main*