Minvera has quit [Remote host closed the connection]
RP has joined #yocto
xmn has quit [Quit: ZZZzzz…]
davidinux has quit [Ping timeout: 268 seconds]
davidinux has joined #yocto
seninha has quit [Ping timeout: 248 seconds]
sakoman has quit [Quit: Leaving.]
xmn has joined #yocto
Thorn has quit [Ping timeout: 260 seconds]
dgriego has quit [Ping timeout: 246 seconds]
dgriego has joined #yocto
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
Estrella has quit [Ping timeout: 260 seconds]
Wouter010067044 has joined #yocto
qschulz_ has joined #yocto
Bardon_ has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Net147 has quit [Read error: Connection reset by peer]
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has joined #yocto
davidinux has quit [*.net *.split]
Wouter01006704 has quit [*.net *.split]
risca has quit [*.net *.split]
Bardon has quit [*.net *.split]
alex88 has quit [*.net *.split]
qschulz has quit [*.net *.split]
otavio has quit [*.net *.split]
dev1990 has quit [*.net *.split]
jsbronder has quit [*.net *.split]
wooosaiiii has quit [*.net *.split]
agrue has quit [*.net *.split]
Wouter010067044 is now known as Wouter01006704
otavio has joined #yocto
Starfoxxes has quit [Ping timeout: 246 seconds]
Starfoxxes has joined #yocto
risca has joined #yocto
agrue has joined #yocto
alex88 has joined #yocto
dev1990 has joined #yocto
wooosaiiii has joined #yocto
jsbronder has joined #yocto
davidinux has joined #yocto
amitk has joined #yocto
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #yocto
Estrella has joined #yocto
Estrella has quit [Ping timeout: 252 seconds]
xmn has quit [Quit: ZZZzzz…]
Thorn has joined #yocto
xmn has joined #yocto
schtobia has quit [Ping timeout: 255 seconds]
schtobia has joined #yocto
amitk_ has joined #yocto
azcraft has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
amitk_ has quit [Ping timeout: 252 seconds]
amitk_ has joined #yocto
manuel1985 has joined #yocto
xmn has quit [Ping timeout: 252 seconds]
manuel1985 has quit [Ping timeout: 248 seconds]
ecdhe_ has quit [Ping timeout: 248 seconds]
rob_w has joined #yocto
amitk_ has quit [Ping timeout: 260 seconds]
hcg has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
vladest has quit [Remote host closed the connection]
amitk_ has joined #yocto
vladest has joined #yocto
ecdhe has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
goliath has quit [Quit: SIGSEGV]
frieder has joined #yocto
amitk_ has quit [Ping timeout: 260 seconds]
amitk_ has joined #yocto
Jham has joined #yocto
zpfvo has joined #yocto
Schlumpf has joined #yocto
PabloSaavedra[m] has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
manuel1985 has joined #yocto
nemik has joined #yocto
goliath has joined #yocto
amitk_ has quit [Ping timeout: 265 seconds]
victoridaho[m] has quit [Quit: You have been kicked for being idle]
mvlad has joined #yocto
amitk_ has joined #yocto
kanavin has quit [Ping timeout: 252 seconds]
kanavin has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
florian has joined #yocto
zpfvo has joined #yocto
Thorn has quit [Ping timeout: 248 seconds]
<phako[m]>
morning, I filed an issue, happy to provide a patch if we can agree on an expected behavior
<phako[m]>
also
<phako[m]>
FileNotFoundError: [Errno 2] No such file or directory: '/home/jgeorg/Projects/Yocto/plain/poky/build-kirkstone/tmp/work/recipetool-mkfea0pu/source/git/example/LICENSE'
<gsalazar>
Hi, I searched in the yocto manual but could not find the set of dependencies to install the SDK, does anyone have a reference to it? I don't want to install all the packages required to build yocto just the ones needed to install the SDK.
<ptsneves>
WHen you mean install, you mean you have already built it and you want to use it in a different host than the one that built it?
<qschulz_>
berton[m]: check if they apply cleanly first (on top of latest commit in dunfell branch), then you could send a patch series to backport it and see what the feedback is on it
<qschulz_>
if the patches aren't in kirkstone or langdale, they probably should make it to those too if they're accepted for dunfell backpot
<gsalazar>
ptsneves: yes, exactly. I want to distribute it to application developers which are not going to build it
<berton[m]>
qschulz_: yes, they apply. I'm using for local builds, I'll send them to mailing list. Thanks!
<ptsneves>
I believe the dependencies are very slim to none. Just extract the SDK and set your tooling to use it. I can only think of the glibc dependency, but that should not be an issue as well. Have you had any issue?
starblue has quit [Ping timeout: 268 seconds]
leon-anavi has quit [Ping timeout: 248 seconds]
<gsalazar>
ptsneves: yes, since the developers are running their tools on a docker container. I had to install at least xz-utils and now I have a error stating that it failed to replace perl and that the relocate scripts failed
starblue has joined #yocto
leon-anavi has joined #yocto
<ptsneves>
gsalazar: cant help, that requires analysis on your part. Even so, do you mean the relocation scripts are in perl? That was not the case last time i checked.
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<gsalazar>
ptsneves: Thanks anyway, the relocation scripts seem to be in python but try to replace the system perl by the SDK perl. In any case I am using an older version and I'll try to investigate
amitk_ has quit [Ping timeout: 248 seconds]
<ptsneves>
That is very odd as that should not happen. If I recall correctly scripts should not need relocation due to using the env as shebang. On the other hand the self extracting sdk should definitely not modify any system things.
gstinocher[m] has quit [Quit: Bridge terminating on SIGTERM]
TRO[m] has quit [Quit: Bridge terminating on SIGTERM]
esben[m] has quit [Quit: Bridge terminating on SIGTERM]
ejoerns[m] has quit [Quit: Bridge terminating on SIGTERM]
barath has quit [Quit: Bridge terminating on SIGTERM]
ericson2314 has quit [Quit: Bridge terminating on SIGTERM]
shoragan[m] has quit [Quit: Bridge terminating on SIGTERM]
phako[m] has quit [Quit: Bridge terminating on SIGTERM]
patersonc[m] has quit [Quit: Bridge terminating on SIGTERM]
mrybczyn[m] has quit [Quit: Bridge terminating on SIGTERM]
Salamandar has quit [Quit: Bridge terminating on SIGTERM]
khem has quit [Quit: Bridge terminating on SIGTERM]
sirhcel[m] has quit [Quit: Bridge terminating on SIGTERM]
AlexanderKrimm[m has quit [Quit: Bridge terminating on SIGTERM]
Quad[m] has quit [Quit: Bridge terminating on SIGTERM]
jclsn[m] has quit [Quit: Bridge terminating on SIGTERM]
karama300[m] has quit [Quit: Bridge terminating on SIGTERM]
lhembed[m] has quit [Quit: Bridge terminating on SIGTERM]
kayterina[m] has quit [Quit: Bridge terminating on SIGTERM]
argonautx[m] has quit [Quit: Bridge terminating on SIGTERM]
playback2396[m] has quit [Quit: Bridge terminating on SIGTERM]
ChristophMayer[m has quit [Quit: Bridge terminating on SIGTERM]
Saur[m] has quit [Quit: Bridge terminating on SIGTERM]
T_UNIX[m] has quit [Quit: Bridge terminating on SIGTERM]
tilman[m] has quit [Quit: Bridge terminating on SIGTERM]
aleblanc[m] has quit [Quit: Bridge terminating on SIGTERM]
Peter[m]1234 has quit [Quit: Bridge terminating on SIGTERM]
KareemZarka[m] has quit [Quit: Bridge terminating on SIGTERM]
p34nuts[m]1 has quit [Quit: Bridge terminating on SIGTERM]
andrewzaza[m] has quit [Quit: Bridge terminating on SIGTERM]
agherzan has quit [Quit: Bridge terminating on SIGTERM]
berton[m] has quit [Quit: Bridge terminating on SIGTERM]
falk0n[m] has quit [Quit: Bridge terminating on SIGTERM]
Chris[m]1234567 has quit [Quit: Bridge terminating on SIGTERM]
glembo[m] has quit [Quit: Bridge terminating on SIGTERM]
PabloSaavedra[m] has quit [Quit: Bridge terminating on SIGTERM]
Archangel[m] has quit [Quit: Bridge terminating on SIGTERM]
jquaresma[m] has quit [Quit: Bridge terminating on SIGTERM]
klesk[m] has quit [Quit: Bridge terminating on SIGTERM]
lrusak[m] has quit [Quit: Bridge terminating on SIGTERM]
khem has joined #yocto
Salamandar has joined #yocto
aak-rookie has quit [Quit: Client closed]
aak-rookie has joined #yocto
shoragan[m] has joined #yocto
mrybczyn[m] has joined #yocto
jquaresma[m] has joined #yocto
TRO[m] has joined #yocto
lrusak[m] has joined #yocto
ericson2314 has joined #yocto
barath has joined #yocto
T_UNIX[m] has joined #yocto
karama300[m] has joined #yocto
argonautx[m] has joined #yocto
gstinocher[m] has joined #yocto
esben[m] has joined #yocto
playback2396[m] has joined #yocto
jclsn[m] has joined #yocto
Chris[m] has joined #yocto
ejoerns[m] has joined #yocto
berton[m] has joined #yocto
Saur[m] has joined #yocto
Archangel[m] has joined #yocto
tilman[m] has joined #yocto
andrew[m]1 has joined #yocto
falk0n[m] has joined #yocto
kayterina[m] has joined #yocto
klesk[m] has joined #yocto
sirhcel[m] has joined #yocto
p34nuts[m] has joined #yocto
lhembed[m] has joined #yocto
KareemZarka[m] has joined #yocto
Quad[m] has joined #yocto
glembo[m] has joined #yocto
agherzan has joined #yocto
phako[m] has joined #yocto
aleblanc[m] has joined #yocto
ChristophMayer[m has joined #yocto
Peter[m]1 has joined #yocto
PabloSaavedra[m] has joined #yocto
AlexanderKrimm[m has joined #yocto
patersonc[m] has joined #yocto
xmn has joined #yocto
<wyre>
hi guys, how may I choose an appropriate sound card for my carrier board? I mean compatible with ALSA
<wyre>
does this depend on the available drivers in the kernel source?
<aak-rookie>
agherzan
<aak-rookie>
performance difference between "meta-raspberrypi" dunfell and kirkstone and did some tests and sharing the resulsts as a table:
zpfvo has quit [Remote host closed the connection]
florian has joined #yocto
<yocton>
Hi, about the newly visible CVE on the yocto kernel. We've seen that most of them are not well defined : matches every kernel version, target kernel but is bluez actually, ... Someone (sakoman? Not 100% sure sorry) mentionned that it was quite simple to send an update to NVD. Can you tell me some details about that process? Where do you send this, with what kind of detail level? Should we justify the update with git logs ?
<sakoman>
yocton: send an email to "cpe_dictionary <cpe_dictionary@nist.gov>" with your justification/links
<sakoman>
If you make a good case with supporting links they usually respond quite quickly
<yocton>
We would need a link that say "Yes, this tag include that commit". I have not seen this on cgit / git.kernel.org. Github mirrors would show this. Which do you think is better git.kernel.org or github mirrors?
<rburton>
yocton: GitHub mirror is good for that. Easiest to start with the latest version where it merged into master.
paulg has quit [Read error: Connection reset by peer]
frieder has quit [Remote host closed the connection]
<yocton>
Ok, thanks! We'll try that and see how it goes
GNUmoon has quit [Ping timeout: 255 seconds]
prabhakarlad has quit [Quit: Client closed]
Minvera has joined #yocto
brazuca has quit [Quit: Client closed]
amitk has quit [Ping timeout: 248 seconds]
ptsneves has joined #yocto
florian_kc has joined #yocto
florian has quit [Ping timeout: 246 seconds]
leonanavi has quit [Quit: Leaving]
knicklicht has joined #yocto
<knicklicht>
Hey all, I am trying to add the recipe for the pipewire project to my yocto (petalinux) build. I get an error: unparsed line: 'GROUPADD_PARAM:${PN} = "--system pipewire"' . I can't find any information on this error. Can someone help me?
kevinrowland has quit [Quit: Client closed]
brazuca has joined #yocto
invalidopcode1 has quit [Remote host closed the connection]
invalidopcode1 has joined #yocto
<rob_w>
knicklicht, maybe your yocto is to old for that syntax
<rob_w>
GROUPADD_PARAM_${PN} is a older way i think
<knicklicht>
How do I find out? I am using Gatesgrath
<rob_w>
try and test
<knicklicht>
Okay, thanks.
knicklicht has quit [Quit: Client closed]
knicklicht has joined #yocto
pbsds has quit [Quit: Ping timeout (120 seconds)]
knicklicht has quit [Ping timeout: 260 seconds]
pbsds has joined #yocto
DvorkinDmitry has joined #yocto
<DvorkinDmitry>
I have two branches for one recipe. Every time I build the image I need to choose customer1 or customer2 I'm building for (branch 1 or branch 2). May I just copy the image1 to image 2 and set PREFFERED_VERSION for my recipe there?
<DvorkinDmitry>
or better give different names for two recipes? or separate them by versions?
azcraft has quit [Remote host closed the connection]
stephano is now known as stephano[away]
stephano[away] has quit [Quit: ZZZzzz…]
kevinrowland has joined #yocto
sakoman has quit [Quit: Leaving.]
<kevinrowland>
${MAKE} is an exported variable from bitbake.conf. Can I change it on a per-task basis? E.g. if I want a do_special_make task that calls base_do_compile, but I want oe_runmake_call to use my special ${MAKE} variable rather than the one exported by bitbake.conf.
<kevinrowland>
I tried `MAKE_task-do_special_make = "my-special-make"` but this didn't have the effect that I'm after -- oe_runmake_call still used bare `make` rather than `my-special-make`
<RP>
kevinrowland: which release is that for?
<Saur[m]>
kevinrowland: That should be `MAKE_task-special_make`, i.e., without the `do_`.
<RP>
Saur[m]: well spotted, yes, that :)
<kevinrowland>
oops, that was just a typo on my part. copy-pasted directly: `MAKE_task-special_make = "echo \"special make\""` -- yes, right now I'm just attempting to prove that this works, so my "special" make command is an echo
<kevinrowland>
I've also tried with export, as in `export MAKE_task-special_make = "echo \"special make\""`. Same results -- ${MAKE} in `oe_runmake_call` seems to be expanded before my override is applied
<Saur[m]>
And you are using Dunfell or some other old release? Otherwise it should of course be MAKE:task-special_make
<kevinrowland>
hardknott, and we just upgraded from warrior so we still have the old syntax
<kevinrowland>
Is this because `oe_runmake_call` says ${MAKE} with curly braces? And bitbake expands that variable while parsing all of the recipes / configuration files?
<RP>
kevinrowland: it is possible the values are exported before the task override is applied, the task override is very late
goliath has quit [Quit: SIGSEGV]
<kevinrowland>
ACK, no problem. I'm going to forgo overriding ${MAKE} and using the existing base_do_compile -> oe_runmake -> oe_runmake path.. I'll just write some custom base_do_special_make and call that from my special task
<RP>
kevinrowland: we should probably check into that and document it if it is the case
<kevinrowland>
ooh, I guess I lurk around here enough that it's time for me to contribute. how do you usually track tasks? informally in IRC or with some ticketing system?
nemik has quit [Ping timeout: 248 seconds]
<Saur[m]>
kevinrowland: I just tested with Langdale, and it seems you are correct. Setting `MAKE:task-compile` has no effect, while setting `MAKE` works as expected.
nemik has joined #yocto
<kevinrowland>
Saur[m]: thank you for checking
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
<Saur[m]>
Hmm, interesting. I searched for other exported variables that are being overridden for tasks, and found `PATH:prepend:task-devshell = "${COREBASE}/scripts/git-intercept:"` (which I incidentally sent a patch to remove the other day), and it seems to work as expected. At least the git-intercept path is in `PATH` when the devshell is running...
Thorn has quit [Ping timeout: 248 seconds]
florian_kc has quit [Ping timeout: 260 seconds]
<Saur[m]>
Ok, another datapoint: if I do `FOO = "make"
<Saur[m]>
FOO:task-compile = "FOOBAR"
<Saur[m]>
MAKE = "${FOO}"` then it works as intended (and fails because `FOOBAR` doesn't exist).
<Saur[m]>
(Insert linebreaks as appropriate.)
<Saur[m]>
kevinrowland: And that btw, should be the workaround you need to do what you wanted to do. ;)
<Saur[m]>
Not sure why it works when using an intermediate variable, but I guess it is some kind of interaction between overriding and exporting the same variable.
stephano has joined #yocto
<kevinrowland>
Wow ok, very interesting. And this `FOO = "make" ... `MAKE = "${FOO}"` logic is all in a recipe? Not a .conf file?