Tokamak has quit [Read error: Connection reset by peer]
dev1990 has quit [Quit: Konversation terminated!]
Tokamak has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
jclsn0 has quit [Ping timeout: 276 seconds]
jclsn0 has joined #yocto
nemik has quit [Ping timeout: 258 seconds]
nemik has joined #yocto
jclsn0 has quit [Ping timeout: 240 seconds]
jclsn0 has joined #yocto
otavio_ has quit [Ping timeout: 240 seconds]
otavio has joined #yocto
Tokamak has quit [Ping timeout: 256 seconds]
Tokamak has joined #yocto
jclsn0 has quit [Ping timeout: 246 seconds]
jclsn0 has joined #yocto
jclsn0 has quit [Ping timeout: 276 seconds]
jclsn0 has joined #yocto
mckoan|away has quit [Ping timeout: 255 seconds]
jclsn0 has quit [Ping timeout: 250 seconds]
sakoman has joined #yocto
jclsn0 has joined #yocto
jclsn0 has quit [Ping timeout: 240 seconds]
starblue has quit [Ping timeout: 256 seconds]
starblue has joined #yocto
camus has joined #yocto
jclsn0 has joined #yocto
jclsn0 has quit [Ping timeout: 276 seconds]
jclsn0 has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Tokamak has quit [Ping timeout: 250 seconds]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
jclsn0 has quit [Ping timeout: 240 seconds]
mckoan|away has joined #yocto
jclsn0 has joined #yocto
jclsn0 has quit [Ping timeout: 255 seconds]
jclsn0 has joined #yocto
jclsn0 has quit [Ping timeout: 246 seconds]
jclsn0 has joined #yocto
jclsn has quit [Ping timeout: 244 seconds]
jclsn0 has quit [Ping timeout: 255 seconds]
jclsn has joined #yocto
jclsn0 has joined #yocto
xmn has quit [Ping timeout: 240 seconds]
ldericher_ has joined #yocto
dkl_ has joined #yocto
Vonter has quit [Ping timeout: 246 seconds]
mlaga97 has quit [Ping timeout: 246 seconds]
ldericher has quit [Ping timeout: 246 seconds]
mckoan|away has quit [Ping timeout: 246 seconds]
dkl has quit [Ping timeout: 246 seconds]
Guest87 has quit [Ping timeout: 246 seconds]
mlaga97 has joined #yocto
Vonter has joined #yocto
mckoan|away has joined #yocto
sakoman has quit [Quit: Leaving.]
kroon has joined #yocto
camus has quit [Remote host closed the connection]
camus has joined #yocto
GNUmoon has quit [Ping timeout: 240 seconds]
peoliye has quit [Quit: Client closed]
goliath has joined #yocto
GNUmoon has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
OnkelUlla has joined #yocto
rob_w has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
fray has quit [Ping timeout: 255 seconds]
goliath has quit [Quit: SIGSEGV]
fray has joined #yocto
frieder has joined #yocto
dev1990 has joined #yocto
mvlad has joined #yocto
mvlad has quit [Client Quit]
mvlad has joined #yocto
olani has quit [Ping timeout: 246 seconds]
olani has joined #yocto
Wouter0100 has quit [Ping timeout: 240 seconds]
Alban[m] has joined #yocto
<Alban[m]>
Hi! I have a recipe that fails compiling, but take more than 1h to build. How can I restart it without having it restart from zero?
<mckoan>
Alban[m]: build it out of Yocto and return into the recipe once you solved the issue in your code
<Alban[m]>
that's not possible, there is tons of dependencies that I can't provide out of yocto
<JaMa>
as long as you don't need to re-run configure you can just hack on it in WORKDIR and when you have something which builds update the recipe
<mckoan>
Alban[m]: you could try with option -c devshell
<Saur[m]>
Alban: If nothing has changed in bitbake's metadata, the build of that recipe will start where it failed. Which typically will result in it failing again...
<mckoan>
Saur[m]: when you call bitbake the whole sources in SRC_URI are rebuild
<kroon>
I thought running the temp/run.* scripts in a "bitbake -c devshell" was about as close as one could get
<Saur[m]>
Well, at least recipes that use Make will just call make, which will start where it was. And I believe it is the same for Meson.
<kroon>
they will not just call make, they will possibly pass make flags aswell. which will be covered by running temp/run.do_compile
<jclsn[m]>
Morning
<Saur[m]>
Though I guess it may behave differently depending on whether ${B} == ${S} or not.
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Schlumpf has joined #yocto
<Saur[m]>
kroon: Of course, what I meant was that I'd you haven't changed the metadata, bitbake will just run the same make command again for that recipe the next time you start bitbake.
<Saur[m]>
if you haven't*
<Saur[m]>
Though typically, if you expect to do a lot of hacking to get the thing building, it is probably easier to just bite the bullet and devtool modify it. An hour is not that much compared to accidentally having the changes wiped because of running something that happens to cause bitbake to remove the source directory...
goliath has joined #yocto
<Alban[m]>
in my experience do_compile always restart from scratch if it fails. I'm most probably hitting an OOM condition or some other limit. Waiting 1 hour for each try is just very very painful
<Alban[m]>
I'll give a try to the devshell
<Alban[m]>
The package is qtwebegine, so it has to build a full chromium which is just a pain.
bps has joined #yocto
bps has joined #yocto
<jclsn[m]>
qschulz: My password issue has still not resolved. Any ideas why?
<Saur[m]>
Alban: If it is an OOM problem your are having, you should see that in the system logs. And you would have to solve that first, because eventually you will have to have bitbake do the full build of the recipe to proceed. Using devshell or devtool modify is typically for when you have build errors that need to be fixed.
<Alban[m]>
the problem is currently my build container just exit and the build log don't show anything interresting. I need a way to just trigger the faulty condition without having to wait hours each time
<Saur[m]>
Is that an automated build, or are you manually starting the build inside the container? Because if it is the former, then the latter should be the solution.
florian has joined #yocto
<Alban[m]>
It's a manual build but I use a rootless podman container to have reproducible environment. Work quiet well normally, but I'm might be hitting a bug in podman
<Saur[m]>
Well, if the container dies as a result of running bitbake, then it definitely sounds like an OOM. But that should show in the system logs...
<Saur[m]>
Unfortunately, I'm no container expert so I can't help much with that.
Circuitsoft has quit [Quit: Connection closed for inactivity]
PatrickE has joined #yocto
<qschulz>
jclsn[m]: I'm pretty sure the issue you're seeing is unrelated to the password being invalid but more that you have the policy of changing the password on first login?
<qschulz>
jclsn[m]: someone seems to have found the issue on the mailing list
<qschulz>
you need to generate a sha512 instead of a sha256
<qschulz>
jclsn[m]: if you could test, it'd be really helpful to us :)
<qschulz>
I'm surprised we didn't hit this issue before
<jclsn[m]>
qschulz: I will give that a try
<jclsn[m]>
Sure :)+
<qschulz>
wondering if it's some kind of DISTRO_FEATURES that is enabled or a specific package being enabled/configured some way that triggers this
<jclsn[m]>
I think 95% of the Yocto developers are very reluctant to upgrade to newer release early
<jclsn[m]>
So it might not have been reported yet
<jclsn[m]>
Of not often enough
<qschulz>
jclsn[m]: you're the second one :)
<qschulz>
so that's already way more than we'd like
<jclsn[m]>
See
<qschulz>
(two too many :) )
<jclsn[m]>
Sure
<jclsn[m]>
But well it is not easy to maintain such a huge and compilcated project perfectly at all times I guess
<qschulz>
jclsn[m]: sure, mistakes happen :) If that's really the issue, we need to figure out if there's a way to write unittests for this (in addition to documenting it obviously)
<qschulz>
jclsn[m]: also, i don't remember but did you test this on vanilla poky with no other layers and no change to the local.conf or something?
<rburton>
Alban[m]: bitbake most definitely doesn't do a full build from scratch if do_compile fails
<rburton>
*if* the build system supports out of tree builds then do_configure will clean the build tree, but do_compile will not
<jclsn[m]>
qschulz: Of course not. I tested it with my setup.
<rburton>
the recipe, or the underlying makefiles, may be doing something dumb, but the expected behaviour is that you can re-run do_compile and it will fail the same, just quicker.
<jclsn[m]>
It seems to login and prompts to change the password right away. I am building the sha512 version ow
<Alban[m]>
rburton: on my machine it always restart from 0, very obvious on large packages like the kernel
<rburton>
the process bar will start from 0 because that's how progress bars work
<Alban[m]>
any idea how I could see make lead to that behavior?
<Alban[m]>
s/make/what/
<rburton>
if you;re doing the build in a container, is the build directory being preserved between runs or is it being deleted and re-created?
lighteagle has joined #yocto
<rburton>
obviously the build tree needs to survive for it to continue
<Alban[m]>
sure, i have the build tree in a mounted volume
<lighteagle>
Hi, I'm new to yocto, tell me please what I'm doing wrong. I am building fsl-image-networking and i need to include iwlwifi drivers in the image. I did through bitbake virtual/kernel -c menuconfig changes, then diffconfig, got fragment.cfg and toss it in my layer, during the build you i see that the process takes longer, but the result is no drivers on the final system.
<rburton>
Alban[m]: for debugging build problems a devshell is best: you can run make by hand, or run what the do_compile task would do by just running temp/run.do_compile directly
<rburton>
lighteagle: if you enabled the driver as modules, you most likely need to add the modules to the image
<rburton>
every module goes into a separate package
<lighteagle>
Yes as modules, what can I change to enable them?
<rburton>
if you have a machine of your own, follow that, otherwise local.conf, image recipe, whatever. they're just a package, install it.
rber|res has joined #yocto
<lighteagle>
no the machine is not custom, i.e. should I change drivers not as a module, and add the package to the local conf?
Schiller has joined #yocto
<jclsn[m]>
qschulz: No, sha512 doesn't work
<rburton>
lighteagle: your system, your choice. if you make it built-in then you don't need to install the package as it's built in to the kernel. if you made it a module, just install the package somewhere.
<jclsn[m]>
It also doesn't tell me to change the password anymore
<qschulz>
jclsn[m]: :/
<jclsn[m]>
Maybe it is a kitty issue
<jclsn[m]>
It has some issues with xterm compatibility
<jclsn[m]>
Will try another emulator
PatrickE has quit [Ping timeout: 252 seconds]
dgriego has quit [Ping timeout: 240 seconds]
<lighteagle>
rburton thank you very much, but apparently I do not understand some simple thing. Basically I don't care how to add them, I'm used to adding new packages via local.conf, and would appreciate any pointers where, what to change, or how to make it easier for a newbie
dgriego has joined #yocto
<jclsn[m]>
But if not, no idea what setting could interfere. Maybe the debug-tweaks are messing with it
Schiller has quit [Quit: Client closed]
<jclsn[m]>
Hmm not a kitty issue apparently
<jclsn[m]>
qschulz: Who is that other user that had issues? Would like to ask him if he solved it
<jclsn[m]>
qschulu: Ah, okay. I think he has another issue. He can login but is prompted to change the password. In my case it tells me that, but doesn't let me in. I had the same issue than him on my Raspberry Pi at home. It told me to change the password, but I could log in
<jclsn[m]>
I am not even getting inside here
<jclsn[m]>
Call of qschulu haha
<jclsn[m]>
qschulz:
argonautx has joined #yocto
<rburton>
lighteagle: easiest is to just set the driver to built-in
<qschulz>
jclsn[m]: you can use tab auto-complete usually in IRC clients :)
<qschulz>
(I know you're on matrix but I'd imagine they have more or less the same shortcut)
<jclsn[m]>
qschulz: Matrix here. I can't connect to the libera server in the company for some reason...
<qschulz>
jclsn[m]: can you login through serial and not ssh or like no-way for both?
<qschulz>
sorry to make you repeat stuff, i forgot most of the issue (if not all :|)
<jclsn[m]>
qschulz: I can change the password via serial. interesting
<jclsn[m]>
only ssh fails
<jclsn[m]>
No worries. I constantly beg for help here. So no problem if I test something for you.
<qschulz>
jclsn[m]: might be some openssh/dropbear limitation?
<qschulz>
e.g. is root user allowed to login from ssh?
<qschulz>
(PermitRootLogin in the openssl conf IIRC?)
<jclsn[m]>
The password is also not long enough it seems
<jclsn[m]>
I only had four chars
<qschulz>
jclsn[m]: "test" :D?
<jclsn[m]>
I am more creative than that
<jclsn[m]>
But now I can log in fine via serial but not ssh
<jclsn[m]>
qschulz: Weird
<jclsn[m]>
Maybe because of dropbear hmm
<lighteagle>
rburton: And through fragment.cfg how to add to the final system? I do not want to change someone else's files.
<jclsn[m]>
qschulz: Yes, dropbear did not permit root login
<jclsn[m]>
I should stop changing too many things at the same time. Makes it hard to get to the bottom of things
Guest73 has joined #yocto
<Guest73>
Hello, May I know how to remove python3 from the host and target sdk package ? TOOLCHAIN_HOST_TASK_remove = " nativesdk-python3-core", seems not to work. The image is built on top of core-image. Python3 is not installed to image. We deliver SDK to project teams and they are complaining that python3 in sdk is causing problems after sourcing the sdk.
<Guest73>
They want to use host python3 to do some analysis.
prabhakarlad has quit [Quit: Client closed]
Guest7380 has joined #yocto
Guest7380 has quit [Client Quit]
tre has joined #yocto
jpuhlman has quit [Ping timeout: 255 seconds]
jpuhlman has joined #yocto
<qschulz>
jclsn[m]: cool thanks for the report. I think we need to list allow-root-login IMAGE_FEATURES in the docs
<rburton>
lighteagle: create your own layer with the kernel bbappend and your login
<qschulz>
michaelo: ^
Sona has joined #yocto
Sona84 has joined #yocto
Sona84 has quit [Client Quit]
manuel1985 has joined #yocto
starblue has quit [Ping timeout: 255 seconds]
Guest73 has quit [Quit: Client closed]
starblue has joined #yocto
Schiller has joined #yocto
<ptsneves>
hey does anybody know where is the linaro presentation on tuxmake? I am not finding it on youtube
<qschulz>
we do mailing list based contribution, no GitHub PR
<jclsn[m]>
Thanks :) So I forked this for nothing haha
locutusofborg has quit [Ping timeout: 244 seconds]
locutusofborg has joined #yocto
<selff>
hello everyone. i wrote a hostname changing script. i want this script to be set to default hostname and stand up like that. if the hostname changes when the system up need to do reboot. i need to set it during boot without requiring a reboot. i prepared the recipe as follows : pastebin.com/qRzDB7xi
<selff>
but it works after the OS is up and i need to reboot in order for the hostname to be set. how can i do it without the need for a reboot?
kroon has quit [Remote host closed the connection]
kroon has joined #yocto
<jclsn[m]>
qschulz: It is in poky/recipes-core, so oe-core mailing list?
<jclsn[m]>
Mainly because my boss forces me to haha
<jclsn[m]>
You guys are probably Gentoo all the way, right?
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
<LetoThe2nd>
jclsn[m]: macOS and ubuntu usually, to be honest.
<jclsn[m]>
Mac User raus
<qschulz>
jclsn[m]: Fedora for me :)
<jclsn[m]>
qschulz: Good boy :)
<qschulz>
we have a bit of everything I think but mostly debian based since it's what most people use for building Yocto projects I believe
* LetoThe2nd
shrugs.
<jclsn[m]>
Ah guess setting up git-email with my company mail won't work
<qschulz>
(via containers otherwise)
<jclsn[m]>
Just asking because bitbake is based on Gentoo
<qschulz>
wasn't aware it's how it started
<qschulz>
don't know if there's much in common today though
<jclsn[m]>
Look at Gentoo eBuilds
<RP>
jclsn[m]: a long time ago, not much of portage is left there
<jclsn[m]>
They look very much like .bb files
<jclsn[m]>
RP: I guess yeah
<LetoThe2nd>
tbh, that argument is like we expect everybody to drive daimler, because the initial car design was by Carl Benz, one of the founders of the company, some 130+x years back.
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<jclsn[m]>
LetoThe2nd: I didn't say everyone should use Gentoo
<jclsn[m]>
I use Manjaro btw
<jclsn[m]>
Mainly because I became too lazy for Arch
ptsneves has quit [Quit: Client closed]
ptsneves has joined #yocto
<RP>
jclsn[m]: the current bitbake maintainer has never used gentoo! :)
<LetoThe2nd>
RP: well... using != running
<jclsn[m]>
RP: Good to know. I will rub that under my Gentoo-fantic colleagues's nose who says "It is best to use Gentoo when you work with Yocto"
* landgraf
uses Gentoo and Fedora
<jclsn[m]>
git-email doesn't work with my mail provider it seems. Can I not just send a patch to the mailing list?
<RP>
jclsn[m]: you can
<RP>
that is all git-email does
pgowda_ has joined #yocto
selff has quit [Ping timeout: 252 seconds]
<jclsn[m]>
Done
Schiller has joined #yocto
<qschulz>
jclsn[m]: not as attachment but mail subject as commit title and mail body as commit log + git diff
selff has joined #yocto
<jclsn[m]>
qschulz: Okay sorry
<qschulz>
jclsn[m]: I use my personal address to send patches to bypass corporate limitations, i understand not everybody wants to do it this way :)
nemik has quit [Ping timeout: 240 seconds]
<jclsn[m]>
I thought that I have to use the one that I registered with and that was my company mail. Else I would rather use my personal
nemik has joined #yocto
<qschulz>
you can register with multiple addresses :)
<jclsn[m]>
Yeah you are right
<jclsn[m]>
Guess I was too lazy
<jclsn[m]>
Another mail to Halstead
<qschulz>
jclsn[m]: I think it's something that maintainers will be willing to do themselves but the commit log should not be indented (let's see ;) )
<qschulz>
that can now be discussed on the mailing list instead :)
<jclsn[m]>
That is why people use Git email I guess
<jclsn[m]>
Maybe I should make a protonmail account
<jclsn[m]>
I still have this shitty web.de address from like 2001 or something
<jclsn[m]>
Just too lazy to switch
<qschulz>
jclsn[m]: no need for something good privacy-wise for just sending patches :)
<jclsn[m]>
Yeah but it didn't work with web.de. It should support tls and ssl, but both did not work
<jclsn[m]>
Can I just register a second mail or do I have to write Halstead again?
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<jclsn[m]>
Ah nevermind
<ramacassis[m]>
hi all, do you know if it is possible to precise a layer when doing "require recipes-kernel/linux/linux.inc" in a recipe ?
<ramacassis[m]>
the file "linux.inc" actually exists in multiple layers and the version I want is not taken
<ramacassis[m]>
meta-atmel [...]/poky/meta-atmel 10 <= the one I want
<ramacassis[m]>
meta-oe [...]/poky/meta-openembedded/meta-oe 6 <= the one which is taken
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<ramacassis[m]>
I guess I can avoid the trouble with a local symlink next to my recipe but it's not very clean =)
Tokamak has quit [Ping timeout: 256 seconds]
<qschulz>
ramacassis[m]: just copy the .inc file otherwise
<ramacassis[m]>
indeed, with a good comment and it will be just fine. Thx !
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
Tokamak has joined #yocto
<ptsneves>
who is the maintainer of python3? With my shebang QA patch python3-native breaks the build because of too big paths
<qschulz>
moto-timo: and rburton are usually the people working the most on Python recipes so would be a safe bet. I guess you could give a bit more info so when they join this chat they have an idea what is being asked
<ptsneves>
gtkdoc is also failing and i am looking into it
rob_w has quit [Remote host closed the connection]
argonautx has quit [Quit: Leaving]
selff has quit [Quit: Client closed]
kroon has quit [Quit: Leaving]
sakoman has joined #yocto
kscherer has joined #yocto
amitk_ has joined #yocto
amitk has quit [Ping timeout: 246 seconds]
<kergoth>
ramacassis[m]: BBPATH order is controlled by BBLAYERS order in bblayers.conf, not by BBFILE_PRIORITY. The latter affects recipe priority, but the former affects file inclusion order. They're not the same unless you set up your bblayers to make it so. Long standing behavior. Somewhere around here I have a bitbake-layers subcommand plugin to add a sort-layers command to align the two on demand.. and some setup scripts do so
<kergoth>
automatically, but most don't
<ptsneves>
on latest master when i do devtool update-recipe python3-native -N i get "ERROR: Unable to determine main branch - please check out the main branch in source tree first" Did anybody ever see this error, or why?
<qschulz>
kergoth: what about the order of inclusion in require/include?
<qschulz>
is it dictated by BBPATH too?
<qschulz>
I blindly answered but completely forgot it wasn't a .conf or .bbclass file...
Guest87 has joined #yocto
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
<kergoth>
qschulz: yeah. inherit/require/include all use it. inherit is just a specialized include, really.
ardo has quit [Ping timeout: 260 seconds]
<qschulz>
kergoth: TIL :)
prabhakarlad has joined #yocto
ardo has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
<qschulz>
ramacassis[m]: sorry for the mislead, nothing to do with layer priorities. spoke too fast :/
nemik has joined #yocto
<ptsneves>
i thought include order was determined by how they appeared in the parsing order
<qschulz>
ptsneves: it's incidental. it's because by default BBPATH is appended to in layer.conf
zoologist has quit [K-Lined]
<qschulz>
but you could prepend to it
<qschulz>
and layer.conf are read in the order in which they appear in BBLAYERS AFAIR
<qschulz>
(please don't prepend to BBPATH :) )
<ptsneves>
do we really need BBFILE_PRIORITY then?
<qschulz>
for recipes and bbappends yes
<Guest87>
is there a way to run a command when bitbake finishes running within bitbake?
<qschulz>
Guest87: what exactly is your usecase?
<Guest87>
qschulz: i wanted to send myself a notification of some variety when a lengthy build is done
<kergoth>
Guest87: see the bitbake user manual, the section about events. various events are fired during a build, when it starts, ends, when tasks run, etc. You'd want the BuildCompleted event. a .inc/.bb/.bbclass can use addhandler to add a python event handler to run then.
fitzsim has joined #yocto
<ramacassis[m]>
<qschulz> "ramacassis: sorry for the..." <- no problem really ! in the end changing the layers order in bblayers.conf (and bblayers.conf.sample) perfectly did the job, thx for the help
goliath has quit [Quit: SIGSEGV]
<ramacassis[m]>
Guest87: if it's just a simple notification on your machine you could use directly the command line
<ramacassis[m]>
$ bitbake <recipe>; zenity --info --text="Compilation done" (or using notify-send, or sendmail, or whatever)
atomic_null[m] has joined #yocto
mckoan is now known as mckoan|away
<ramacassis[m]>
(doubtful that it answers your need but we never know =) )
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
cmd has quit [Remote host closed the connection]
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
<kergoth>
ramacassis[m]: yeah, sometimes that's for the best :) not *everything* has to be done within bitbake..
frieder has quit [Remote host closed the connection]
Schlumpf has joined #yocto
goliath has joined #yocto
florian has quit [Quit: Ex-Chat]
<moto-timo>
bitbake make me a sandwich
florian_kc has quit [Ping timeout: 255 seconds]
<kergoth>
hehe. There was a long standing joke that bitbake could do anything you told it to do, including order a pizza. I'm not sure anyone ever bothered actually doing it, though :)
Schlumpf has quit [Quit: Client closed]
<michaelo>
qschulz: thanks for the suggestion about "allow-root-login". I added it to my todo list.
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #yocto
bps has quit [Ping timeout: 244 seconds]
manuel1985 has quit [Quit: Leaving]
peoliye has joined #yocto
<RP>
kergoth: there are things you don't do with bitbake? :) I thought we even planned pizza ordering!
florian_kc has joined #yocto
bps has joined #yocto
bps has joined #yocto
marex has quit [Ping timeout: 255 seconds]
alimon has joined #yocto
leon-anavi has quit [Quit: Leaving]
goliath has quit [Quit: SIGSEGV]
paulbarker_ has joined #yocto
jonmason_ has joined #yocto
praneeth_ has joined #yocto
ad__ has joined #yocto
georgem_ has joined #yocto
jamestperk_ has joined #yocto
mithro_ has joined #yocto
karl_ has joined #yocto
tperrot_ has joined #yocto
zoologist has joined #yocto
paulbarker has quit [Ping timeout: 248 seconds]
jquaresma[m] has quit [Ping timeout: 248 seconds]
jonmason has quit [Ping timeout: 248 seconds]
bigendian has quit [Ping timeout: 248 seconds]
ejoerns[m] has quit [Ping timeout: 248 seconds]
mithro has quit [Ping timeout: 248 seconds]
khem has quit [Ping timeout: 248 seconds]
tperrot has quit [Ping timeout: 248 seconds]
mborges has quit [Ping timeout: 248 seconds]
jackos888[m] has quit [Ping timeout: 248 seconds]
praneeth has quit [Ping timeout: 248 seconds]
georgem has quit [Ping timeout: 248 seconds]
karl has quit [Ping timeout: 248 seconds]
jonmason_ is now known as jonmason
jamestperk has quit [Ping timeout: 248 seconds]
mithro_ is now known as mithro
praneeth_ is now known as praneeth
paulbarker_ is now known as paulbarker
georgem_ is now known as georgem
jamestperk_ is now known as jamestperk
<rburton>
ptsneves: at a conference but if you mail me something I might be able to look later
khem has joined #yocto
jquaresma[m] has joined #yocto
ejoerns[m] has joined #yocto
mborges has joined #yocto
jackos888[m] has joined #yocto
<yudjinn[m]>
can someone help me understand what the error message "No recipes available for: ....bbappend" means?
<zeddii>
yudjinn[m]: the bbappend has to match the recipe name, and version, unless you use the % wildcard for the version. it's telling you that there's no match
goliath has joined #yocto
mvlad has quit [Remote host closed the connection]
<yudjinn[m]>
That makes sense, thanks!
PatrickE has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Guest87 has quit [Quit: Connection closed]
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
marex has joined #yocto
PatrickE has quit [Ping timeout: 252 seconds]
amitk_ has quit [Ping timeout: 240 seconds]
amitk has joined #yocto
amitk has quit [Ping timeout: 258 seconds]
amitk has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
amitk has quit [Ping timeout: 258 seconds]
amitk has joined #yocto
Schiller has quit [Ping timeout: 252 seconds]
peoliye has quit [Quit: Client closed]
bps has quit [Ping timeout: 250 seconds]
<yudjinn[m]>
Im using the meta-tegra dunfell-32.6.1 branch when building and getting a "drivers/net/usb/lan78xx.c: patch does not apply", I couldnt find any info about it and was wondering if anyonehad ideas
kscherer has quit [Quit: Konversation terminated!]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
lighteagle has quit [Read error: Connection reset by peer]