tolnanwo has quit [Remote host closed the connection]
tolnanwo has joined #yocto
hoyes73 has quit [Ping timeout: 248 seconds]
nerdboy has quit [Ping timeout: 252 seconds]
Jones42 has joined #yocto
Knogle has quit [Quit: WeeChat 4.4.2]
Jones42 has quit [Ping timeout: 276 seconds]
nerdboy has joined #yocto
qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #yocto
ablu has quit [Ping timeout: 272 seconds]
ablu has joined #yocto
AdrianF5 has joined #yocto
AdrianF has quit [Ping timeout: 260 seconds]
AdrianF5 is now known as AdrianF
jclsn has quit [Ping timeout: 248 seconds]
jclsn has joined #yocto
xmn has quit [Ping timeout: 265 seconds]
sotaoverride has joined #yocto
sotaover1ide has joined #yocto
sotaoverride is now known as Guest7353
sotaover1ide is now known as sotaoverride
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
geoff__ has joined #yocto
geoff_ has quit [Ping timeout: 245 seconds]
PhoenixMage has quit [Ping timeout: 255 seconds]
PhoenixMage has joined #yocto
tammranil has quit [Remote host closed the connection]
tammranil has joined #yocto
Guest27 has joined #yocto
<Guest27>
hi
dario has quit [Ping timeout: 244 seconds]
<Guest27>
hello yocto team i have one issue found in embedded build system , the issue i have used meta-odroid layer and i have using kirkstone release to build odroid-xu4 linux custom image but the problem is this image is not show output on hdmi through connected LCD and any monitor how to enable this feature to support hdmi.
Guest27 is now known as arniju
<arniju>
please give me response for my this problem ??
DixitP has joined #yocto
dario has joined #yocto
tyzef has joined #yocto
tolnanwo has quit [Remote host closed the connection]
<arniju>
hello yocto team i have one issue found in embedded build system , the issue i have used meta-odroid layer and i have using kirkstone release to build odroid-xu4 linux custom image but the problem is this image is not show output on hdmi through connected LCD and any monitor how to enable this feature to support hdmi.
<Dvergatal>
rburton: but it started to work again, odd...
ptatrai has joined #yocto
dmoseley has joined #yocto
dmoseley_ has quit [Ping timeout: 252 seconds]
jclsn has quit [Quit: WeeChat 4.4.3]
jclsn has joined #yocto
ddee has joined #yocto
ddee51 has joined #yocto
<ddee51>
Can someone please explain how the environment setup scripts should be managed when multiple architectures are involved? Specifically, how should the selection process work when multiple scripts are installed?"
ddee has quit [Ping timeout: 256 seconds]
jclsn has quit [Quit: WeeChat 4.4.3]
Guest51 has joined #yocto
pgowda has joined #yocto
Guest51 has quit [Quit: Client closed]
florian has joined #yocto
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 260 seconds]
<rburton>
Dvergatal: we stopped using that as a connectivity check URL in 2016...
<rburton>
RP: bah ok thanks
leon-anavi has joined #yocto
<rburton>
RP: i think we've a problem with python rebuilds as it can't wipe the build tree
<rburton>
i had to force a rebuild of numpy earlier
<agodard>
moto-timo: sure, let me know if you want me to create a bug and describe it there, so we can start a discussion
jclsn has joined #yocto
rob_w has joined #yocto
mckoan|away is now known as mckoan
<arniju>
can you suggest me how to run any embedded board custom image on qemu emulator in yocto project
<arniju>
[11:15:41] <arniju> hello yocto team i have one issue found in embedded build system , the issue i have used meta-odroid layer and i have using kirkstone release to build odroid-xu4 linux custom image but the problem is this image is not show output on hdmi through connected LCD and any monitor how to enable this feature to support hdmi.
<arniju>
[11:30:39] ← steelswords94 has left (Quit: The Lounge - https://thelounge.chat)
<RP>
rburton: that shouldn't affect the autobuilder though :/
ddee51 has quit [Quit: Client closed]
mathieudb has quit [Ping timeout: 252 seconds]
davidinux1 has joined #yocto
mathieudb has joined #yocto
mathieudb has quit [Changing host]
mathieudb has joined #yocto
<Dvergatal>
rburton: thx
<rburton>
RP: double bah. maybe numpy is just terrible at parallel builds.
davidinux1 has quit [Ping timeout: 265 seconds]
davidinux1 has joined #yocto
<RP>
rburton: maybe. I don't know how much of -next is valid or not at this point :/
GNUmoon has joined #yocto
davidinux1 has quit [Ping timeout: 265 seconds]
davidinux1 has joined #yocto
ddee has joined #yocto
arniju has quit [Quit: Client closed]
DixitP has quit [Quit: Client closed]
Deepesh has joined #yocto
florian has quit [Ping timeout: 245 seconds]
<usvi>
how can I list what compilers are used exactly to build my image? is it available if I print the environment?
<mckoan>
usvi: AFAIK you can't
<mckoan>
usvi: or at least you can run 'file anyexecutable' on your target system
davidinux1 has quit [Ping timeout: 252 seconds]
<usvi>
well this is troubling
<usvi>
my workmate manages to build different checksummet binaries from the same sources and I am trying to figure out wtf
aduskett has joined #yocto
<usvi>
funny thing even the pkg versions are the same in opkg list-installed (or whatever it was)
ddee has quit [Quit: Client closed]
davidinux1 has joined #yocto
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #yocto
ddee has joined #yocto
florian has joined #yocto
<Jones42>
usvi: are you speaking of the whole image or just a single package binary?
<Jones42>
what i sometimes do, is to edit the run.do_compile file, add some debug stuff and simply re-run it: ./run.do_compile
<usvi>
Jones42: I have some c/c++ projects included in the image I'm interested about
pgowda has quit [Quit: Client closed]
tyzef has joined #yocto
<Jones42>
usvi: I'm by far no expert, but I found the temp folder very helpful. It shows you exactly which things are being executed during configure/compile/...
<usvi>
ok thanks, I will take a look
<Jones42>
(note: not "tmp", but tmp/work/**/<packagename>/<version>/temp)
prabhakalad has quit [Ping timeout: 245 seconds]
<usvi>
thanks
prabhakalad has joined #yocto
davidinux1 has quit [Ping timeout: 260 seconds]
<rburton>
usvi: for native stuff your host compiler is used, but for target then its the gcc-cross recipe
<rburton>
usvi: you can use something like diffoscope to compare the two binaries and see if the difference is silly things like build paths, or actual different code generation/linkage
davidinux1 has joined #yocto
tyzef has quit [Quit: WeeChat 3.8]
jclsn has quit [Quit: WeeChat 4.4.3]
ddee has quit [Ping timeout: 256 seconds]
<usvi>
rburton: alright. I'm no expert but I would assume that regardless of paths, the binaries would be the same
ddee has joined #yocto
<usvi>
rburton: We have the same virtual machine given to him and to me years ago
<usvi>
he must have messed his up somehow
<rburton>
usvi: that's a rash assumption
<usvi>
because our virtual machines are the our way of ensuring identical build environment
<rburton>
build paths can be embedded in binaries, and builds may be non-deterministic in nature
<rburton>
both of which are bugs but can happen
<usvi>
for image level differences I don't mind and I know they will probably happen, but single executable changes are the bothering thing for me
<rburton>
we spent a lot of effort making oe-core build reproducibily, it's not a given
<rburton>
but diffoscope will tell you where the differences are and if they're subtle or major
<JaMa>
sakoman: can you please check why https://lists.openembedded.org/g/openembedded-core/message/189665 was backported to dunfell, but doesn't seem to be included in kirkstone? with pipes removed in python-3.13 it's one of reasons why kirkstone doesn't parse with python-3.13 on host, I'll send backport request shortly (I though I already did, but when searching my inbox I've found only this dunfell request
<JaMa>
instead)
<sakoman>
JaMa: probably just an oversight . I've cherry-picked it now, so no need to send a request
<JaMa>
already done, feel free to ignore the e-mail :)
sukbeom has joined #yocto
<sakoman>
JaMa: Thanks for catching that!
<JaMa>
np, using bleeding edge gentoo for some builds help me catch all weird stuff :)
<JaMa>
and using container with ubuntu-24.10 for kirkstone buidls helps to catch some other missing backports
<sakoman>
JaMa: I appreciate the help :-)
Grogu68 has quit [Quit: Client closed]
Grogu68 has joined #yocto
Grogu75 has joined #yocto
DixitP has joined #yocto
Deepesh has quit [Quit: Client closed]
ptsneves has joined #yocto
tgamblin__ has joined #yocto
tgamblin_ has quit [Ping timeout: 260 seconds]
tgamblin__ is now known as tgamblin
ddee has joined #yocto
cyxae has joined #yocto
DixitP has quit [Ping timeout: 256 seconds]
<Grogu75>
My first yocto question: what does "yocto project" mean? Is it the name of the _effort_ to develop a tool (yocto) and/or it's the name of the tool? I find it used both ways. Is it simply ambiguous?
<RP>
Grogu75: The Yocto Project collects together a number of tools/techniques/people/infrastructure to make building custom OSes easier
<RP>
Grogu75: so it is the name of the overall effort and is an umbrella project name
<Grogu75>
so both ... was thinking that even though no one has said that clearly till now
Grogu75 has quit [Quit: Client closed]
ddee has quit [Ping timeout: 256 seconds]
steelswords94 has joined #yocto
ddee has joined #yocto
geoff__ has quit [Ping timeout: 248 seconds]
vermaete has joined #yocto
<vermaete>
question: is meta-ros maintained?
<vermaete>
Last commits on it is some months ago.
<vermaete>
Although ROS and meta-ros has some many names, releases and branches I'm not sure I'm looking at the correct place.
<gmorell>
any hints on packaging pyproject.toml-based dependencies, my deb is missing the actual python code for whatever reason. I've added the prepend as described here https://stackoverflow.com/a/78324351/2821302 to the recipe, but I'm still ending up with a deb that is missing the actual python library and only has the headers
<JonasJalling>
Hello, what is the general consensus. I have two almost identical machines - same arch, similar rootfs, similar kernel config. If I want to apply different kernel patches and configuration in general, do I make a layer for each machine, or do I do machine overrides in the different recipes?
<JonasJalling>
Well, it\s actually more than two, but the concept is the same - only small changes between them. I tend towards creating a machine layer for each, but I don\t know if its over the top
JonasJalling has quit [Quit: Client closed]
<gmorell>
figured it out by using python_poetry_core instead of setuptools