ecdhe has quit [Read error: Connection reset by peer]
Guest53 has quit [Client Quit]
Guest53 has joined #yocto
davidinux has quit [Ping timeout: 268 seconds]
davidinux has joined #yocto
Guest53 has quit [Quit: Client closed]
sakoman has quit [Quit: Leaving.]
starblue has quit [Ping timeout: 264 seconds]
starblue has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
ecdhe has joined #yocto
seninha has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
sakoman has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
jclsn has quit [Ping timeout: 260 seconds]
jclsn has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<moto-timo>
@kiwi_29_[m] posting the same exact content three times does not improve the chances of a response
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
Lihis has quit [Quit: Quitting]
guest13215 has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
Lihis has joined #yocto
guest13215 has joined #yocto
sakoman has quit [Quit: Leaving.]
prabhakarlad has quit [Ping timeout: 244 seconds]
alessioigor has joined #yocto
effem has joined #yocto
<effem>
Hi, can annyone provide me with a link or info on how to get started with gcc-sanitizers? if I link with -fsanitize=leak I get linker errors (a.o missing -llsan)
Vonter has quit [Ping timeout: 264 seconds]
Vonter has joined #yocto
ptsneves has joined #yocto
mvlad has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
<LetoThe2nd>
yo dudX && mckoan
rfuentess has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
zpfvo has joined #yocto
Schlumpf has joined #yocto
Schiller has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
<xcm>
hello! the procps recipe doesn't seem to install a init.d/procps file (or anything else that runs sysctl). is this functionality provided elsewhere?
<xcm>
LetoThe2nd: hmm, it does install sysctl, but no init.d file in sigh (in that .bb, or in my system)
<LetoThe2nd>
xcm: then you probably need to add the file with the payload you need.
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 268 seconds]
camus1 is now known as camus
zpfvo has quit [Ping timeout: 252 seconds]
prabhakarlad has joined #yocto
manuel1985 has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
xmn has quit [Read error: Connection reset by peer]
xmn has joined #yocto
manuel1985 has quit [Remote host closed the connection]
manuel1985 has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
berton[m] has joined #yocto
zpfvo has joined #yocto
xmn has quit [Ping timeout: 255 seconds]
vladest has quit [Ping timeout: 260 seconds]
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
mrpelotazo has quit [Ping timeout: 246 seconds]
manuel_ has joined #yocto
mrpelotazo has joined #yocto
GNUmoon has quit [Remote host closed the connection]
manuel1985 has quit [Ping timeout: 255 seconds]
GNUmoon has joined #yocto
manuel_ has quit [Read error: Connection reset by peer]
nucatus has quit [Remote host closed the connection]
manuel1985 has joined #yocto
nucatus has joined #yocto
zhmylove has joined #yocto
manuel_ has joined #yocto
manuel1985 has quit [Ping timeout: 272 seconds]
manuel_ has quit [Ping timeout: 272 seconds]
manuel_ has joined #yocto
florian has joined #yocto
Schlumpf has quit [Ping timeout: 244 seconds]
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
Schiller has joined #yocto
manuel1985 has joined #yocto
Schlumpf has joined #yocto
manuel_ has quit [Ping timeout: 260 seconds]
<Schlumpf>
Hi, I have multiple layers overwriting kernel configs. Is there a simple way to figure out, where the resulting config came from?
camus has quit [Ping timeout: 252 seconds]
camus has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
<qschulz>
Schlumpf: I think this info should be available in the log.do_fetch log file of your recipe
manuel_ has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
mrpelotazo has quit [Read error: Connection reset by peer]
manuel1985 has quit [Ping timeout: 272 seconds]
eadan_ has joined #yocto
<Schlumpf>
qschulz: Maybe my question wasn't precise enough. I would like to see, where a specific config option came from. For example there is the option CONFIG_BT enabled by deconfig, then disabled by a .cfg in first layer and enabled again in another fragment.cfg in a second layer. There are some more options, where I don't know who enabled or disable
<Schlumpf>
them.
manuel1985 has joined #yocto
mrpelotazo has joined #yocto
manuel_ has quit [Ping timeout: 272 seconds]
manuel_ has joined #yocto
manuel1985 has quit [Ping timeout: 252 seconds]
manuel1985 has joined #yocto
zpfvo has joined #yocto
manuel_ has quit [Ping timeout: 246 seconds]
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
manuel1985 has quit [Remote host closed the connection]
eadan_ has quit [Quit: Konversation terminated!]
nemik has quit [Ping timeout: 272 seconds]
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
nemik has joined #yocto
Estrella_ has quit [Remote host closed the connection]
Estrella_ has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
zpfvo has joined #yocto
nucatus_ has joined #yocto
nucatus has quit [Ping timeout: 252 seconds]
manuel1985 has joined #yocto
manuel1985 has quit [Remote host closed the connection]
camus has quit [Ping timeout: 260 seconds]
manuel1985 has joined #yocto
nucatus_ has quit [Remote host closed the connection]
nucatus has joined #yocto
camus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
<rburton>
JPEW: thanks. that spdx patch looked suspicious :)
effem has quit [Ping timeout: 244 seconds]
eadan has joined #yocto
<eadan>
Hi, I'm setting up ptests for some of our internal python packages. I found this example `run-ptest` boilerplate used accross a lot of recipes in poky so have adopted it for ours, only I'm not sure its working as expected. When its run ptest-runner is reporting "Total: 1 FAIL: 0" when i can see quite clearly in the output a lot of problems. Is this the expected behaviour? i.e. is FAIL: 0 saying it succeeding in running all
<ad__>
hi, in a task function, how can i test a .conf variable ?
Estrella has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<rburton>
they're just variables, so d.getVar() if its python, or usual shell testing on ${VARIABLENAME}
<ad__>
rburton: thnaks
<ad__>
mm, only issue, do_configure_prepend is not re-executed if the variable changes
<ad__>
i need to -c cleanall
<ad__>
oh, sry, it is re-executed, but sources stays the old
<eadan>
Having looked through the source of ptest-runner it looks as if the FAIL count is purely if the test failed to run, not a count of the number of tests that returned a result of fail.. it's presumably then left to manual review or another wrapping process to determine the overall status?
<vvn>
meta-oe's wvdial has musl-support.patch in SRC_URI but also has COMPATIBLE_HOST:libc-musl = "null"
<vvn>
khem: hi -- is there a reason for not having musl support for wvdial?
<JaMa>
vvn: probably because of wvsterams, see bf7670ff2e0e555a9ac2492dad0a69d552ac2757 where it was added
xmn has joined #yocto
<JaMa>
wwstreams
<vvn>
JaMa: almost ;-D
<vvn>
wvstreams*
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
hcg has quit [Ping timeout: 244 seconds]
<JaMa>
what can you do with only 1L of coffee :)
<rburton>
michaelo: how's the documentation going? are we good to call it done, or do you prefer to wait until eg monday?
<ad__>
is there a way to force a "git checkout -- ." of the source tree always from the bb recipe ?
zpfvo has quit [Ping timeout: 255 seconds]
sakoman has joined #yocto
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 255 seconds]
zpfvo has joined #yocto
rnekhf has quit [Ping timeout: 252 seconds]
Schiller has joined #yocto
Schiller has quit [Client Quit]
zpfvo has quit [Ping timeout: 255 seconds]
zpfvo has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
alessioigor has quit [Quit: alessioigor]
arielmrmx has joined #yocto
mrpelotazo has quit [Ping timeout: 246 seconds]
mrpelotazo has joined #yocto
<qschulz>
ad__: what is your issue?
<zhmylove>
abelloni: hi, are you here? I'd like to ask you about sanity problem with ext4. I've minimized the change to only one diff: https://git.yoctoproject.org/poky-contrib/commit/?h=szhmylev/binary_repeatable_fstab&id=ef6eb83854a8b7b5cc74ca3df9afe532a881d62c But it still fails due to fsck.ext4 fixes timestamp in the future (year 2072)
Minvera has joined #yocto
<ad__>
qschulz: for some reasons, i am copying 2 source files in git tree, on do_configure_prepend, conditioanally, if a variable is set. Unsetting the variable, modified sources stays still there
marc1 has quit [Ping timeout: 252 seconds]
<qschulz>
ad__: how would it know the sources have changed between two builds?
seninha has joined #yocto
<ad__>
i am copying 2 sources in place of using patch, based on a variable. So seems a bad way
<qschulz>
ad__: I guess you could have do_patch[vardeps] +=
<qschulz>
"YOUR_VARIABLE" or something like that
<qschulz>
which would trigger a do_patch again
<qschulz>
or maybe do_unpack?
<qschulz>
the one that is getting rid of the source directoyr (likely unpack)
<qschulz>
but I think something's not bent the right way for you to have to do this?
<qschulz>
can't you just use conditional patches in SRC_URI?
<ad__>
do_patch[vardeps] seems to work. Thanks really
kscherer has joined #yocto
marc1 has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
Schlumpf has quit [Quit: Client closed]
nemik has quit [Ping timeout: 246 seconds]
<abelloni>
zhmylove: yeah, I'm not quite sure where this timestamp is coming from
nemik has joined #yocto
<abelloni>
it is possibly something specific to how buildtools are built
seninha has quit [Quit: Leaving]
rfuentess has quit [Remote host closed the connection]
<khem>
vvn: The patch fixes some but not all issues, so yes patches are welcome
<vvn>
khem: ho ok, that's a work in progress, got it.
Estrella__ has quit [Read error: Connection reset by peer]
Estrella_ has quit [Ping timeout: 255 seconds]
florian_kc has joined #yocto
zpfvo has quit [Quit: Leaving.]
<zhmylove>
abelloni: ok, it looks like SOURCE_DATE_EPOCH is being set randomly during the build. I'll send the new version of the patch soon
zhmylove has quit [Quit: Leaving]
seninha has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
ecdhe has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
florian_kc has joined #yocto
PhoenixMage has quit [Ping timeout: 248 seconds]
PhoenixMage has joined #yocto
sakoman has quit [Quit: Leaving.]
PhoenixMage has quit [Ping timeout: 255 seconds]
PhoenixMage has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
<vvn>
what's the reasoning for having pci and pcmcia in distro features in addition to machine features?
<vvn>
I mean it seems weird for a distro to decide not to support arbitrary pci devices. I'd rather imagine packagegroups for machine specific features such as usbhost, pci, pcmcia, etc. be dependencies of packagegroup-machine-base.
<abelloni>
you could have pci on a platform and not care about any of the tools
<vvn>
abelloni: in that scenario you would exclude packagegroup-base-pci, no?
<vvn>
it's not just the tools though, but the driver modules as well
<JaMa>
also MACHINE_FEATURES predate packagegroups quite a bit, in old oe-classic we had task-* recipes with just a RDEPENDS as a convention (e.g. recipes/tasks/task-qt4-x11.bb) which lead to packagegroups later and there weren't many task-* recipes and MACHINE_FEATURES was mostly used to define what recipes/tasks/task-base.bb should pull into the image
<vvn>
do you guys rely on packagegroup-base* for your production images?
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
roussinm has joined #yocto
barometz has quit [Quit: you can't fire me!]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
barometz has joined #yocto
vladest has joined #yocto
sakoman has joined #yocto
vladest1 has joined #yocto
ecdhe has joined #yocto
vladest has quit [Ping timeout: 252 seconds]
vladest1 is now known as vladest
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
ecdhe has quit [Remote host closed the connection]
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 246 seconds]
nucatus has joined #yocto
nemik has joined #yocto
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
florian_kc has quit [Ping timeout: 272 seconds]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
Minvera has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
nucatus has quit [Remote host closed the connection]
nucatus has joined #yocto
mvlad has quit [Remote host closed the connection]
prabhakarlad has joined #yocto
<derRichard>
is DL_DIR supposed to be shareable among different users? although i have proper ACLs installed to give every user rwx permissions i see crazy build errors.
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
<cambrian_invader>
how can I reuse a build directory for oe-selftests
<cambrian_invader>
I am working on a selftest and I don't want to have to wipe and restart every time I change something
vladest has quit [Remote host closed the connection]
vladest1 has joined #yocto
nemik has quit [Ping timeout: 258 seconds]
nemik has joined #yocto
vladest1 is now known as vladest
<cambrian_invader>
ok apparently the solution is to use -j1 (WTF???)
mark_ has joined #yocto
mark_ is now known as mark_l
<mark_l>
I am trying to debug this error from Kirkstone "ERROR: Parsing halted due to errors, see error messages above", but there are no ERROR message in the log, seems like something so wrong it exited before the error message got printed out. What log files would be most helpful to debug this and where can I find it?
florian_kc has joined #yocto
<JaMa>
did you check bitbake-cookerdaemon.log? or tried it with -DDD?
vladest has quit [Read error: Connection reset by peer]
<mark_l>
Thanks! -DDD helped me found it, did not know this option until now
vladest has joined #yocto
florian_kc has quit [Ping timeout: 258 seconds]
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
vladest has quit [Read error: Connection reset by peer]