<RP>
ernstp: it is an override, just an inactive one
<abelloni>
ffmepg, binutils and valgrind failures
<ernstp>
RP: thanks! PACKAGECONFIG:remove:pn-gdb = "readline" is the correct syntax!
amsobr has quit [Quit: Konversation terminated!]
starblue has quit [Ping timeout: 260 seconds]
starblue has joined #yocto
amsobr has joined #yocto
<mckoan>
LetoThe2nd: you have mail
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Guest23 has joined #yocto
<Guest23>
Hello,
<Guest23>
I am adding a python file to my Yocto image by simply copying the file. Unfortunately no __pycache__ folder and .pyc file is generated by the build system, despite my recipe inherits python3native.
<Guest23>
How can I convince the build to generate those?
glgspg[m] has joined #yocto
zpfvo has quit [Ping timeout: 260 seconds]
BrianL has quit [Quit: Client closed]
starblue has quit [Quit: WeeChat 3.8]
<kanavin>
ernstp, I wonder why you need to do that. Are you shipping gdb in a gpl3-less product to customers?
zpfvo has joined #yocto
florian_kc has joined #yocto
<JaMa>
I guess setting P_V_readline to old version from meta-gplv2 (to be used by some other components shipped to customers) and then gdb fails because readline is too old
AndreRicardo has joined #yocto
<ernstp>
kanavin: it's a bit more complicated, with a developer image and a release image. But I can't have per-image license setup, so it was easier this way...
<kanavin>
ernstp, why not? per-image licensing restrictions have been available for a long time
<ernstp>
kanavin: oh! I didn't find that. can you give me a pointer?
<ernstp>
(i'm on Kirkstone right now btw)
<kanavin>
ernstp, IncompatibleLicensePerImageTests() in meta/lib/oeqa/selftest/cases/incompatible_lic.py has examples
<kanavin>
ernstp, I see we still haven't documented it :-(
<ernstp>
kanavin: ah, that's probably why I didn't find it :-)
<kanavin>
NoGPL3InImagesTests also shows a few ways to tweak images
<ernstp>
ok, looks simple enough. I'll try it out, thanks!
<kanavin>
ernstp, the trick is to postpone the licensing check to the actual rootfs of the image. a bitbake build can build anything it wants, as long as it doesn't end up in the image.
<ernstp>
Yeah, that's what I really wanted of course!
<ernstp>
an with :pn-my-image it is like that I assume then...
mischief has quit [Ping timeout: 245 seconds]
mischief has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
<Guest23>
Hi again, can someone point me to where/when the __pycache__/*.pyc files are generated in Yocto? (my python files does not get precompiled)
<ernstp>
Guest23: usually by having something like inherit python_setuptools_build_meta in your recipe
<adrianf>
Guest23: In the past there was Python setuptools only. Now there are several build frameworks for Python available. You might choose one of the modern tools or use setuptools. With setuptools you need to add a setup.py file to your source code repository. If the setup.py file is available you can add "inherit setuptools3" to your recipe and
<adrianf>
everything will just work magically.
rob_w has quit [Remote host closed the connection]
<Salamandar>
Hello everyone, I have a syntax issue
<Salamandar>
I’ve SRC_URI and SRC_URI_myarch (yeah, dunfell syntax, don’t shoot the messenger)
<Salamandar>
How could I have this same override for SRC_URI[sha256sum] ? bitbake doesn’t like SRC_URI[sha256sum]_myarch, and SRC_URI_myarch[sha256sum] doesn’t work
<jonmason>
stupid question, how do I specify a specific version of a package for a build requirement? I can do so for the entire image (via PREFERRED_VERSION_foo) in local.conf, but when I specify in the recipe it gets only the latest version.
AndreRicardo has quit [Ping timeout: 246 seconds]
bunk has quit [Quit: leaving]
goliath has quit [Quit: SIGSEGV]
florian has quit [Quit: Ex-Chat]
florian_kc has quit [Ping timeout: 245 seconds]
<RP>
kanavin: patches to add the docs are even better thanks :)
<khem>
abelloni: I have a new binutils patch on yoe/mut, it has a failure in valgrind on x86 which is fixed
<kanavin>
jonmason, you can't build two version of the same component in a single setup, so specifying versions in recipes doesn't make much sense
zpfvo has quit [Remote host closed the connection]
astlep5504 has joined #yocto
<JPEW>
RP: Ya, that's my guess as the actual problem. The rest is all just cleanup
rfuentess has quit [Quit: chela!]
mixfix41 has joined #yocto
Guest62 has quit [Quit: Client closed]
astlep5504 has quit [Remote host closed the connection]
<RP>
JPEW, vmeson: The arm ltp test results count correlates with which worker it was run on. The slower 1804 machine has the low counts, the 2204 faster hardware has the higher counts
astlep5504 has joined #yocto
alimon has quit [Remote host closed the connection]
<RP>
JPEW: the bug is even simpler, the commands are just timing out on the older/slower system :(
<RP>
JPEW: the timeout error is being ignored
<JPEW>
Ah, I wondered about that too
* RP
found the evidence once I knew which system to look on
alimon has joined #yocto
alimon has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
frieder has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Zappan has quit [Ping timeout: 250 seconds]
Zappan has joined #yocto
<abelloni>
khem: I'll queue this up later on with the glibc one
<khem>
so I guess, it comes down to poky fork perhaps getting the above change but then not reverting it while oe classic reverted it somewhere. Lets see
sakoman has quit [Quit: Leaving.]
<khem>
oh its still in classic oe master nm
yates_work has joined #yocto
<yates_work>
can someone please suggest a link (or a book) for cross-compiling?
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
argonautx[m] has joined #yocto
yates_work has left #yocto [rcirc on GNU Emacs 29.0.92]
amitk has quit [Ping timeout: 260 seconds]
sakoman has joined #yocto
<mischief>
is there a simple way to remove `ensurepip` from python3-misc in the final image?
<mischief>
(besides just rming it in an image task..)
<vvn>
what machine should we use in order to boot the generated image in a systemd-nspawn container? qemux86-64 for an x86_64 host?
<mischief>
vvn: probably.
leon-anavi has quit [Quit: Leaving]
<khem>
yates: what are you particularly looking for ? c/c++ cross compiling irrespective of yocto ?
<khem>
vvn: yes that right machine or you can also use genericx86-64 if you are using the meta-yocto-bsp layer
<khem>
meta-intel has intel-corei7-64 or intel-skylake-64 which might be a bit specific but depends on what you need
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<RP>
khem: Seems I was guilty of something 15 years ago? :)
goliath has joined #yocto
BWhitten has joined #yocto
<khem>
Oh yes future crimes
<khem>
I am not sure though, it might be still needed, I am trying to reproduce the x32 issue which bewilders me a bit
alessioigor has quit [Quit: alessioigor]
<khem>
RP: how do we configure x32 for testing on AB
<khem>
ah seems just set DEFAULTTUNE = 'x86-64-x32' and use normal qemux86-64
<RP>
khem: config.json in yocto-autobuilder-helper or look at the logs on the autobuilder, but yes
<RP>
JPEW, vmeson 600s of timeout gets us 50% of the results instead of 25% :(
<JPEW>
Ouch
BWhitten has quit [Ping timeout: 245 seconds]
<RP>
I think we should disable some of the tests :/
rber|res has quit [Ping timeout: 240 seconds]
* RP
throws 1200 at it just to see if it completes
rber|res has joined #yocto
<abelloni>
I'd go for 1260 ;)
florian_kc has joined #yocto
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mvlad has quit [Remote host closed the connection]
sakoman has quit [Quit: Leaving.]
gsalazar has quit [Ping timeout: 246 seconds]
<jonmason>
1024
pabigot has quit [Ping timeout: 245 seconds]
pabigot has joined #yocto
florian_kc has quit [Ping timeout: 246 seconds]
Kubu_work has quit [Quit: Leaving.]
Xagen has joined #yocto
sakoman has joined #yocto
<JaMa>
anyone seeing do_image_wic tasks getting stuck forever (probably due to syslinux process getting stuck even from some previous build)?