<Ch^W>
Yup... confirmed... EdgeOS is, and as far as I can tell always has been, Debian based. TIL...
<Ch^W>
Given all the work they did to hack in Vyatta... it feels like an odd choice.
<Ch^W>
RP: I should be able to do a deep dive on the setup tools stuff, but not until after OSSNA in June. Not sure how the fits with scheduling, but that is the best I can do at the moment.
<khem>
openmp-src is built with one of clang runtime recipes, is there an easy way for me to look into data to see what could have changed in the package between two runs ?
<khem>
basically diffoscope output
<RP>
khem: if you look at the logs you'll see an path with a url in it
<khem>
yeah I see there is a date embedded in there with one of generated files
Chaser has joined #yocto
<RP>
khem: that looks to be the issue
<khem>
RP: I have another issue in nativesdk-clang to fix and then we are good with a-quick
goliath has quit [Quit: SIGSEGV]
<RP>
khem: sounds good. I've not looked at those patches yet. Struggling with 5.2 :/
florian_kc has joined #yocto
Jones42 has quit [Ping timeout: 252 seconds]
Kubu_work has joined #yocto
<tgamblin>
how does one adjust the size of /var/volatile in a Yocto image? I'm building core-image-minimal and there's only 4.0K available. Is this possible to configure in local.conf?
druppy has quit [Ping timeout: 265 seconds]
* tgamblin
wonders if this is even something he wants to do
wmills_ has quit [Remote host closed the connection]
<tgamblin>
rburton: what I'm trying to do ultimately is fix the numpy ptests, but it looks like ~100 (or somewhere south of that many) ptests are trying to write to files... but since that's happening in /var/volatile/tmp, there's not enough space
goliath has joined #yocto
<rburton>
ah fun, probably following a link from /tmp
<rburton>
try creating a temporary directory under cwd and redirecting TMPDIR, if it respects that
<tgamblin>
rburton: thanks, will try it
<rburton>
also fwiw core-image-ptest adds a lot more space to the rootfs for this reason
<rburton>
and you can bitbake core-image-ptest-python3-numpy to get an image with just the numpy tests in
<tgamblin>
rburton: right
<tgamblin>
rburton: looks like it just ends up using 2G of storage created. core-image-ptest.bb suggests that there's a functional upper limit for the image size, so I'm not sure if specifying a much larger IMAGE_ROOTFS_EXTRA_SPACE in there for python3-numpy?
ello_ has quit [Read error: Connection reset by peer]
ello has joined #yocto
ello_ has joined #yocto
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
enok has joined #yocto
cyxae has joined #yocto
cyxae has quit [Remote host closed the connection]
cyxae has joined #yocto
cyxae has quit [Client Quit]
enok has quit [Ping timeout: 245 seconds]
sakoman has quit [Ping timeout: 265 seconds]
sakoman has joined #yocto
druppy has joined #yocto
Kubu_work has quit [Quit: Leaving.]
<rburton>
tgamblin: only because it’s trying to fit in specific image type limits. Easily ignored if you use wic images. Surely you don’t need gigabytes?