azcraft has quit [Remote host closed the connection]
Tokamak_ has quit [Ping timeout: 255 seconds]
Tokamak_ has joined #yocto
seninha has quit [Remote host closed the connection]
rber|res has joined #yocto
RobertBerger has quit [Ping timeout: 260 seconds]
kscherer has quit [Quit: Konversation terminated!]
Tokamak_ has quit [Ping timeout: 256 seconds]
Tokamak_ has joined #yocto
jclsn has quit [Ping timeout: 256 seconds]
jclsn has joined #yocto
invalidopcode7 has quit [Remote host closed the connection]
invalidopcode7 has joined #yocto
gho has quit [Ping timeout: 268 seconds]
gho has joined #yocto
mckoan_ has joined #yocto
mckoan|away has quit [Ping timeout: 256 seconds]
pml has joined #yocto
sakoman has quit [Quit: Leaving.]
grma has quit [Ping timeout: 260 seconds]
thomasd13 has joined #yocto
amitk has joined #yocto
sion33 has joined #yocto
goliath has joined #yocto
alessioigor has joined #yocto
vmeson has quit [Ping timeout: 260 seconds]
<brabander>
morning
d-fens_ has quit [Read error: Connection reset by peer]
<LetoThe2nd>
yo dudX
olani has quit [Ping timeout: 256 seconds]
olani has joined #yocto
tomzy_0 has joined #yocto
rob_w has joined #yocto
mvlad has joined #yocto
mckoan_ is now known as mckoan
<mckoan>
good morning
<tomzy_0>
morning
frieder has joined #yocto
* alessioigor
waves all
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
manuel1985 has joined #yocto
zpfvo has joined #yocto
<landgraf>
(^_^)/
goliath has quit [Quit: SIGSEGV]
amgedr has joined #yocto
gsalazar_ has joined #yocto
amgedr has quit [Quit: Leaving...]
<tomzy_0>
Got a question
<tomzy_0>
basically I am using Yocto mostly for generating custom embedded OS for couple of platforms.
<tomzy_0>
Is using Yocto for manage multiple software projects (like hundreds of them) something common?
xmn has quit [Ping timeout: 255 seconds]
<tomzy_0>
If yes, are there some presentations or materials about that?
<LetoThe2nd>
tomzy_0: you mean, more like a binary distribution upstream that the projects can share?
<tomzy_0>
maybe? :P not sure what I mean TBH, just thinking of Yocto is used in cases without any specific platform. But yeah, your scenario makes sense
<tomzy_0>
LetoThe2nd Let's say we want to publish some binaries, using Yocto for that makes sense? We could probably use generic x86 machine for that. Maybe try some generic ARM machine configs (?) to try support other architectures?
<qschulz>
tomzy_0: anything different from a full image binary will not make sense
<qschulz>
if you're planning to build .deb/.rpm binaries for people to use on any system, Yocto is not for that
<qschulz>
Yocto is for *building distributions*
<LetoThe2nd>
well, it depends a bit if you ask me.
<qschulz>
LetoThe2nd: it's the same as asking if I can use Debian package feed on your Yocto image
<qschulz>
or maybe I missed something entirely (wouldn't me a first :) )
<LetoThe2nd>
the lines between building a highly standardized distro (many do that) and providing a statically linked binary application can be quite blurry occasionally. but yeah, if your concern is mostly about the application, then i would also say that its not a yocto story.
<qschulz>
yeah it's not the same thing as some desktop SW vendors do with just providing an rpm/deb for major distributions and then expecting this to work everywhere :)
tor_ has joined #yocto
mvlad has quit [Remote host closed the connection]
goliath has joined #yocto
tor_ has quit [Client Quit]
tor_ has joined #yocto
tor has quit [Ping timeout: 260 seconds]
tor_ is now known as tor
prabhakarlad has joined #yocto
<tomzy_0>
LetoThe2nd: , qschulz as always, thanks for ideas and knowledge
<LetoThe2nd>
yw
leon-anavi has joined #yocto
gchamp has quit [Ping timeout: 268 seconds]
gchamp has joined #yocto
mvlad has joined #yocto
tomzy_0 has quit [Quit: Client closed]
d-fens_ has joined #yocto
seninha has joined #yocto
florian has joined #yocto
<mcfrisk>
how do force rebuild of initramfs? It doesn't seem to get regenerated after kernel changes. old initramfs seems to be pulled form sstate when kernel changed and main rootfs got regenerated. or I'm missing something..
tomzy_0 has joined #yocto
tomzy_0 has quit [Client Quit]
florian_kc has joined #yocto
tomzy_0 has joined #yocto
<mcfrisk>
did not have prserv enabled, and two different kernel compilations result in different kernel signing keys. could that be the reason why initramfs doesn't regenerate if kernel changes?
nemik_ has quit [Ping timeout: 260 seconds]
nemik_ has joined #yocto
<RP>
mcfrisk: the sstate hashes are based on inputs so the system won't have any way to know that the same input would result in different output
nemik_ has quit [Ping timeout: 252 seconds]
nemik_ has joined #yocto
tomzy_0 has quit [Quit: Client closed]
<mcfrisk>
RP: yes, but still this is odd. I forced linux-yocto recompile, then compiled main image which got re-generated. But initramfs doesn't get recompiled. With prserv the version numbers would change, and show that initramfs and main rootfs have different versions of kernel modules. something doesn't add up..
<RP>
mcfrisk: that does seem odd as a force would cause the hashes to change. It sounds like some dependency isn't functioning correctly
<ThomasRoos[m]>
ptest question - wonder if it's a good idea when writing a ptest for a lib to have just a RDEPENDS:${PN}-ptest to another package using that lib, or more packages using that lib? Idea is that this should ensure that the program can be build (and run?) when using that e.g. upgraded lib.
<rburton>
we rebuild everything when stuff changes, so "my app doesn't work anymore" is less of a problem as it would have been rebuilt
<ThomasRoos[m]>
hmm. but this does not make sure that when stuff changes it can run, only be built? right?
<Payam>
hi guys
<Payam>
I never needed to create a virtual machine I linux.
tor_ has joined #yocto
<rburton>
ThomasRoos[m]: right, but presumably the tests for the library run.
<Payam>
so what I want to try here is try out kuksaval server and send some can signal to it.
<Payam>
and I want to do it all in linux
<Payam>
is there any GUI CAN program for linux that reads a database and sends them
tor has quit [Ping timeout: 272 seconds]
Tokamak_ has quit [Quit: Tokamak_]
<rburton>
i suspect this is the wrong channel for questions like that
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
sion33 has quit [Ping timeout: 252 seconds]
sion33 has joined #yocto
<Payam>
rburton, so let me explain more. I want to boot up a GUI yocto image. and send CAN signals to it. Do I download Virtuab box or is there any emulator I can use?
<rburton>
yocto comes with runqemu
<rburton>
which has complete integration if you build a machine with eg MACHINE=qemux86-64
<rburton>
qschulz: if you're looking, you should change that to a backport of the merged commit
<qschulz>
rburton: not looking at the right one ;)
<qschulz>
but I was about to nag you about this one too :)
marc1 has quit [Quit: WeeChat 3.6]
ajfriesen has joined #yocto
marc1 has joined #yocto
goliath has quit [Quit: SIGSEGV]
nemik_ has quit [Ping timeout: 256 seconds]
nemik_ has joined #yocto
nemik_ has quit [Ping timeout: 264 seconds]
nemik_ has joined #yocto
zhmylove has joined #yocto
tangofoxtrot has quit [Remote host closed the connection]
zhmylove has quit [Client Quit]
sion33 has quit [Ping timeout: 246 seconds]
tangofoxtrot has joined #yocto
<qschulz>
rburton: I sent the patch for cairo just before, didn;t know you were actually to do it :)
<qschulz>
s/to do/doing/
<rburton>
ha, sorry
<rburton>
though i'd do it whilst it was open
<qschulz>
rburton: don't worry, i'm fine if yours taken too, doesn't matter to me :)
<qschulz>
though I'm more interested if you were planning to work with upstream cairo on CVE-2019-6462
<qschulz>
(the assert to if change)
<qschulz>
(full disclaimer, I need to fix those CVEs in Buildroot :) and I don't know if they'll like this patch, so better avoid a discussion if something's started somewhere :) )
frieder has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
gsalazar_ has quit [Ping timeout: 272 seconds]
<qschulz>
rburton: actually, the patches for CVE-2019-6461 and CVE-2019-6462 are swapped :)
<qschulz>
i'm wondering why there's a CVE for an assertion instruction? how is this exploitable?
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #yocto
<rburton>
qschulz: ffs
gsalazar_ has joined #yocto
IlanT has joined #yocto
leon-anavi has quit [Quit: Leaving]
<IlanT>
I am following youtube livecoding for yocto project for SDK session 4. When i try to exercise for extensible SDK session , I could install the ext_sdk but when I used bitbake build simplehello , i am getting this error: unable to find any recipe { administrator@administrator-Precision-7760:~/Yocto_new$ devtool build simplehello
<IlanT>
WARNING: attempting to use the extensible SDK in an environment set up to run bitbake - this may lead to unexpected results. Please source this script in a new shell session instead.
<IlanT>
Sstate summary: Wanted 0 Found 0 Missed 0 Current 0 (0% match, 0% complete)
<IlanT>
NOTE: No setscene tasks
<IlanT>
NOTE: Executing Tasks
<IlanT>
NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and all succeeded.
<IlanT>
INFO: Using default source tree path /home/administrator/sdk_ext/workspace/sources/simplehello
<IlanT>
NOTE: Starting bitbake server...
<IlanT>
INFO: Recipe /home/administrator/sdk_ext/workspace/recipes/simplehello/simplehello_git.bb has been automatically created; further editing may be required to make it fully functional
Payam has quit [Read error: Connection reset by peer]
flynn378_ is now known as flynn378
nohit_ has joined #yocto
nohit has quit [Ping timeout: 252 seconds]
Starfoxxes has quit [Ping timeout: 252 seconds]
otavio has quit [Ping timeout: 252 seconds]
Tartarus has quit [Ping timeout: 252 seconds]
jamestperk has quit [Ping timeout: 252 seconds]
nohit_ is now known as nohit
jamestperk has joined #yocto
Tartarus1 has joined #yocto
tokamak[m] has quit [Ping timeout: 252 seconds]
tokamak[m] has joined #yocto
goliath has joined #yocto
Starfoxxes has joined #yocto
gsalazar_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
florian has quit [Quit: Ex-Chat]
azcraft has joined #yocto
seninha has joined #yocto
xantoz has quit [Read error: Connection reset by peer]
xantoz has joined #yocto
Guest60 has joined #yocto
gsalazar_ has quit [Ping timeout: 252 seconds]
<Guest60>
is there a command I can use to see which recipe is pulling another recipe to be installed into the final image? i.e, if there's a recipe called B that's being installed, how can I figure out which recipe is requesting B to be installed via RDEPENDS?
<kergoth>
oe-depends-dot can help you figure that out after running a bitbake -g <yourimage>
ecdhe_ has quit [Read error: Connection reset by peer]
goliath has quit [Quit: SIGSEGV]
ecdhe has joined #yocto
seninha has quit [Remote host closed the connection]
goliath has joined #yocto
<jonmason>
is there a easy way to speed up fetch times? I'm seeing 80k/s trying to get the kernel sources to run a menuconfig
<jonmason>
It'll be like 2h at this rate
<JaMa>
linux-yocto sources? binutils usually take longest from yp mirror, but the easy way is to never delete downloads directory
<JaMa>
and share it as premirror with as many builders as you can
<jonmason>
doing all that fun stuff
<jonmason>
its for gatesgarth, which I probably pruned
<jonmason>
git clone of the linux-yocto tree is giving me 9MB/s
<jonmason>
so I'm just going to use devtool to reference this tree and build from it
<jonmason>
just trying to see if there is a smarter way
seninha has joined #yocto
seninha has quit [Remote host closed the connection]
seninha has joined #yocto
<RP>
jonmason: I think we changed the mirror config in later releases somehow to help for some of these cases. I don't remember what we did
<RP>
JPEW: don't suppose you had any further thoughts on sockname?
mvlad has quit [Remote host closed the connection]
<JPEW>
I can't see how it would do that
<JPEW>
I think some sort of "outside observer" (strace et. al.) is still going to be the best option. strace annoyingly won't traces threads and not subprocesses though
pml has quit [Ping timeout: 272 seconds]
<JPEW>
err, threads and not child processes
<RP>
JPEW: I can't see it either but the logs say it did :/
* RP
is freezing, going to have to do something about more heating tomorrow
<JPEW>
I mean obviously it _happened_, just not in a logical way you would expect from reading the code
<JPEW>
Which means either A) the code is doing something unexpected or B) something outside of the code is doing it
<JPEW>
Ah, OK. We can make it do threads but not forks
<JPEW>
(strace that is)
<RP>
JPEW: I think strace will be a nightmare to interface :(
<JPEW>
RP: Maybe
<JPEW>
I have a PoC, just need to figure out how to make it generic enough
<JPEW>
abelloni: Ack, I left a debug print in that argparse patch
<JPEW>
Sending V4 :(
<abelloni>
I feel like my current build is never going to end...
olani has joined #yocto
<JPEW>
RP: You won't like the top patch on https://git.yoctoproject.org/poky-contrib/log/?h=jpew/bitbake-server-strace , but the patch below that will let you strace e.g. `bitbake --server-wrapper="/usr/bin/strace -f -b execve -o trace.txt -e unlink --seccomp-bpf" ...`
<JPEW>
If bitbake server is unlinking, that will find it
gsalazar_ has joined #yocto
prabhakarlad has joined #yocto
goliath has quit [Quit: SIGSEGV]
<JPEW>
RP: I suppose if we wanted to make this less "public" we could trigger it just as easily with an envvar instead of a command line argument
gsalazar_ has quit [Ping timeout: 272 seconds]
florian has quit [Ping timeout: 252 seconds]
<RP>
JPEW: we can't really run all the builds on the autobuilder under this until it reproduces :/