<wkawka>
Hi, if recipe fetches files, for example git repo, does it run setup files automatically?
<wkawka>
Or maybe I have to run them via do_install
thomasd13 has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
<LetoThe2nd>
wkawka: you mean if bitbake automatically runs some kind of script shipped with the sources? no. depending on the build system you use, like autotools, cmake, meson, there are classes you can inherit and which are probably doing most of the magic right away.
mckoan|away has quit [Quit: Quitting irssi IRC Client, bye.]
mckoan has joined #yocto
<mckoan>
good morning
goliath has quit [Quit: SIGSEGV]
<LetoThe2nd>
yo dudX && mckoan
frieder has joined #yocto
mvlad has joined #yocto
leon-anavi has joined #yocto
Schlumpf has joined #yocto
gsalazar has joined #yocto
<wkawka>
My recipe requires python-rsa and it is added do RDEPENDS in this recipe, but nothing provides it. Where can i add this?
<wkawka>
I have to create a recipe in meta-python?
<wkawka>
or just locally
<wkawka>
And if it is locally, how can I make an order to build, or if sometjing will be in RDEPENDS it will automatically set that order
<LetoThe2nd>
wkawka: in your local layer, meta-python can just serve as examples. yes, dependencies will be handled automatically.
<wkawka>
Ok, thank you very much
<LetoThe2nd>
have fun!
goliath has joined #yocto
<ThomasRoos[m]>
I did my first bugfix patch - it got accepted in master-next and now is in master. What should I do with the still open bugzilla bug? How is the workflow? How will it be closed? Should I add a reference to the commit? thx
<wkawka>
Now I have tried to build a recipe from tar.gz archive, but i have a strange error ```No such file or directory: '/build/tmp/work/recipetool-6v09g70z/work/recipe-sysroot'```. Have you ever encountered something like that?
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
<jclsn>
The hardest task as a Yocto developer: Making your boss understand why a build server with 1TB is just not sufficient if multiple teams are to work on it
<Schlumpf>
jclsn: so true...
<ThomasRoos[m]>
just tell him we can do it with less than 1TB, but then it will take longer time ;)
<RP>
jclsn: remind them that you're building a complete operating system from scratch including debug symbols and data for everything. That does require some space.
<RP>
jclsn: the key is often to highlight how much time you'd waste trying to manage on insufficient space
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
xmn has quit [Quit: ZZZzzz…]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
drivux has joined #yocto
khem has quit [Quit: You have been kicked for being idle]
<drivux>
Hello there. I have different sources directory (fsl-community-bsp) managed by the repo utility. They are: 3 different meta-freescale, meta-openembedded, meta-qt5 and poky. What's the best way to "backup" them to another Gitlab repository?
khem has joined #yocto
<qschulz>
hello people :)
<qschulz>
back from holidays, will not go through the IRC backlog so if anyone asked something to me, feel free to ask again :)
denisoft81 has joined #yocto
tre has joined #yocto
<denisoft81>
hi guys, kindly, how can I do if I receive a segmentation fault error when I import sounddevice python library? Sometimes I get the "Segmentation Fault" error while other times "Aborted" during import. Until the last shutdown, everything was working correctly
<drivux>
qschulz: hello. I just asked how to "backup" a bunch of meta folder managed by the repo utility in a fresh new repository.
florian has joined #yocto
<LetoThe2nd>
denisoft81: strace + meditation what you did before the last shutdown.
Baehrune has joined #yocto
<denisoft81>
I have started a py script for a test and it worked, after shutdown the same operation, had the result of which I asked for help
<LetoThe2nd>
denisoft81: well, possible options are that something else in the system changed, like some library, or that you busted the system by improper shutdown.
gs1234 has joined #yocto
<denisoft81>
I haven't changed anything, so only an improper shutdown could have happened. In this case how can I check or fix it?
<LetoThe2nd>
denisoft81: reflash the device.
<denisoft81>
ok thanks a lot
Baehrune has quit [Ping timeout: 240 seconds]
<gs1234>
Hi guys, I tried out the Yocto cve-check class today for the first time and got hundreds of CVE reported in the logfile. However, while going through the CVE list in the log, I se that most of the packages that have been reported already have a version higher than the one described in the cve summary. Is this pointing to false positives or am I
<gs1234>
just reading the report wrong? Here is an example:
<gs1234>
LAYER: meta
<gs1234>
PACKAGE NAME: libidn2
<gs1234>
PACKAGE VERSION: 2.3.2
<gs1234>
CVE: CVE-2019-12290
<gs1234>
CVE STATUS: Patched
<gs1234>
CVE SUMMARY: GNU libidn2 before 2.2.0 fails to perform the roundtrip checks specified in RFC3490 Section 4.2 when converting A-labels to U-labels. This makes it possible in some circumstances for one domain to impersonate another. By creating a malicious domain that matches a target domain except for the inclusion of certain punycoded Unicode
<gs1234>
characters (that would be discarded when converted first to a Unicode label and then back to an ASCII label), arbitrary domains can be impersonated.
jpuhlman has quit [Remote host closed the connection]
<mrybczyn[m]>
gs1234: by default the tool reports all patched and unpatched issues
<mrybczyn[m]>
gs1234: see the CVE STATUS line
<mrybczyn[m]>
gs1234: you're probably interested in those with Unpatched status
<gs1234>
Oh, I assumed that the status of patched means that the maintainer of the package has released a patch to fix the issue and not that it's already patched in my build
<gs1234>
Here is an example of an unpatched report:
<gs1234>
LAYER: meta
<gs1234>
PACKAGE NAME: unzip-native
<gs1234>
PACKAGE VERSION: 1_6.0
<gs1234>
CVE: CVE-2022-0529
<gs1234>
CVE STATUS: Unpatched
<gs1234>
CVE SUMMARY: A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.
<wkawka>
when I simply add them to rdepends, nothing provides them
gchamp has joined #yocto
starblue has quit [Ping timeout: 276 seconds]
starblue has joined #yocto
<rburton>
gs1234: the cve summary doesn't have to contain the version, follow the link and look at the CPE
<gs1234>
Thanks for the hint. I went to cve link in the patched isuue that I posted above. I can see there that the page also mentions that the issue only impacks version below 2.2.0
<ptsneves>
rburton regarding the upgrade to ntirpc is it acceptable that libnss-native does not support RPC?
<rburton>
possibly
leon-anavi has quit [Remote host closed the connection]
<ptsneves>
ok. Otherwise the whole upgrade is a no-go due to circular dependency. Although honestly i do no see the need for RPC in libnss native
<jclsn[m]>
RP: Thanks. I have all the arguments. I already said this half a year ago. To me it is pretty clear that you need a machine as big as possible with the outlook of having multiple teams build on it. But well, bosses always want to save money and don’t do something unless you prove the necessity to them…
leon-anavi has joined #yocto
jpuhlman has joined #yocto
jpuhlman has quit [Remote host closed the connection]
<RP>
jclsn[m]: you hourly rate vs the time this is costing you won't convince them? :(
nemik has quit [Ping timeout: 256 seconds]
nemik has joined #yocto
jpuhlman has joined #yocto
jpuhlman has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
jpuhlman has joined #yocto
denisoft81 has quit [Quit: Leaving]
rfuentess has quit [Ping timeout: 256 seconds]
<jclsn>
RP: Guess my hourly rate is too low :P
Xagen_ has joined #yocto
<jclsn>
Well, honestly I haven't calculated it through. I am currently running some test with out DevOps guy, which seems to come to the same conclusion. Actually it is not bad to have proof before you blindly buy something. I am just frustrated because to me this has been fairly obvious the whole time ^^
<jclsn>
s/with out/with our/
Xagen has quit [Ping timeout: 276 seconds]
seninha has joined #yocto
<qschulz>
jclsn: depending on the time you spent getting those numbers, it could have been cheaper to just buy the hardware already
<wkawka>
I have an error with do_fetch. I set an uri for a direct download link (before, I set onlu SHA and MD5 sums and result was the same), but do fetch omits version numbers from uri, then i have this error: Resolving files.pythonhosted.org (files.pythonhosted.org)...
<wkawka>
Connecting to files.pythonhosted.org (files.pythonhosted.org)
<wkawka>
HTTP request sent, awaiting response... 404 Not Found
<wkawka>
2022-07-04 11:04:21 ERROR 404: Not Found.
<jclsn>
qschulz: I know right...
<qschulz>
wkawka: what's the actual SRC_URI you're using?
<rfuentess>
rookie question reading recipes at poky/
<rfuentess>
do_compile() and do_install() if not giving in the recipe take place ? E.g. if in custom recipe A I put one of poky's lib (recipe B) in DEPENDS and RDEPENDS. The B's do_compile happens due `DEPENDS` and B's do_install() due the B's library is required ?
<rfuentess>
or am I mixing everything ?
<rfuentess>
(probably that)
<qschulz>
rfuentess: DEPENDS="B" in recipe A will trigger a build of packages built by recipe B
<qschulz>
DEPENDS requests that B build outcomes be put into the sysroot of recipe A so they can be linked against or the header files used during compilation of recipe A
<qschulz>
technically do_compile and do_install are triggered only by DEPENDS="B"
<qschulz>
an explicit RDEPENDS is usually only required if your piece of SW is dynamically loading a shared lib (dlopen) or executing a binary with e.g. system()
<qschulz>
otherwise bitbake will find the packages to include based on the recipes in DEPENDS
<qschulz>
do_install is a task that basically installs files in a temporary directory mimicking the final root filesystem skeleton
<qschulz>
out of this, the sysroot of this recipe is created so some directories and files of this temporary directory can be available to other recipes duriung build time
<qschulz>
and it also is from this directory that files are split into separate packages that can be installed in the final rootfs that'll be used on your target
<qschulz>
rfuentess: there's an "inherit autotools" there
<rfuentess>
I just trying to understand the mechanism and consequences of adding recipe B to A'S `DEPENDS`, a default "make" and "make install" is happening, for that temporary directory?
<rfuentess>
oh, thanks for that URL, not sure why I was not finding it in my google search. Probably because I was using solely "yocto" as keydword xD
Wouter01001 has quit [Read error: Connection reset by peer]
Wouter01001 has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
Lemur-for-rent has quit [Quit: Client closed]
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
<rfuentess>
qschulz: ah. Looking at autotools_do_install() I'm starting to understand where I'm on my extended recipe. Thanks!
manuel1985 has quit [Remote host closed the connection]
manuel1985 has joined #yocto
manuel1985 has quit [Quit: Leaving]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
kroon_ has quit [Quit: Leaving]
ToolboxBunny has joined #yocto
MitchGaines has joined #yocto
vvn has quit [Quit: WeeChat 3.5]
vvn has joined #yocto
vvn has quit [Client Quit]
vvn has joined #yocto
vvn has quit [Client Quit]
vvn has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
leon-anavi has quit [Quit: Leaving]
vvn has quit [Client Quit]
Net147 has quit [Ping timeout: 255 seconds]
Net147 has joined #yocto
Net147 has joined #yocto
sakoman has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
<rfuentess>
qschulz: thanks for the URL. Suddenly I was able to understand all the monster happening behind the lines on the recipes Xd. Libnl's is a little tricky as there are 4 packages on that recipe, but still I'm getting progress
vvn has joined #yocto
<LetoThe2nd>
is there any best practise if in a specific layer, only one recipe has a dependency on another layer?
<LetoThe2nd>
how to best define that?
thomasd13 has quit [Ping timeout: 240 seconds]
<qschulz>
LetoThe2nd: make another layer just for that recipe?
<RP>
qschulz: we've missed you :)
<mckoan>
LetoThe2nd: what's the point?
<LetoThe2nd>
qschulz: yeah that is obviously the escalation solution
<qschulz>
RP: awww, thanks :) (yes I know I'm reviewing patches that are already merged :D)
<LetoThe2nd>
mckoan: the point is that everything else in the layer happily builds without the dependency layer, so unless you want to build that one recipe you probably don't need/want it.
<qschulz>
triaging 3.7k new mails right now, damn mailing list subscribptions :)
<qschulz>
LetoThe2nd: what about BBFILES_DYNAMIC?
<LetoThe2nd>
qschulz: fwd to /dev/null
florian has joined #yocto
<LetoThe2nd>
qschulz: yeah i've though about it but it kinda reverses the logic. only good solution though, it iseem.
<LetoThe2nd>
*seems, even.
<qschulz>
LetoThe2nd: the only issue is that it makes this recipe/package not available in case the layer is noit included
ToolboxBunny has quit [Quit: Client closed]
<qschulz>
so it's a bit hidden away and maybe not easy to debug for users
<LetoThe2nd>
qschulz: yeah
<qschulz>
LetoThe2nd: also, you can have layers inside layers
<qschulz>
so you don't technically need a new git repo
<LetoThe2nd>
qschulz: don't get me started on that, please.
amitk_ has joined #yocto
<qschulz>
LetoThe2nd: have you heard about repo?
<qschulz>
:p :p
<qschulz>
RP: I drove the motorcycle/did hikes for two weeks in North of Slovenia, Dolomites and a bit of Austria. 2700km in 14 days on the bike, 30-40km of hikes I guess? I didn't count those.
amitk has quit [Ping timeout: 240 seconds]
<qschulz>
Super lucky with the weather, only a day and a half of rain
* LetoThe2nd
ponders throwing somthing sharp and pointy. alternatively, having a drink.
<RP>
qschulz: that sounds like a good time :). I was wishing I had a motorcycle most of the time I was in the Dolomites!
<qschulz>
RP: got a flat tire in the middle of nowhere in Slovenia though, no cell service and all.. shouldn't have driven on dirt tracks with an overinflated almost slick tire but eh
<qschulz>
a friend managed to fix it
<RP>
qschulz: these things happen, adds to the adventure
<RP>
qschulz: I've a long list of breakdowns and other issues but mostly they were part of the adventure :)
<qschulz>
surprisingly, many tourists already. we had hoped to avoid most of it but it wasn't actually that easy to find same-day accommodations
<agherzan>
khem: have you ever seen host contamination on go projects while using musl?
<agherzan>
Something like:
<agherzan>
`/usr/include/x86_64-linux-gnu/bits/stdio2.h:100: undefined reference to `__fprintf_chk'`
<zeddii>
RP: I have perf building with the QA warning fixed. patch shortly.
mitch_ has joined #yocto
mitch_ has quit [Remote host closed the connection]
MitchGaines has quit [Remote host closed the connection]
<ptsneves>
when using git send-email do you guys also set --in-reply-to=?
<qschulz>
ptsneves: no, I think this is when you want to send a patch as part of an already existing thread?
<ptsneves>
yes. Sorry. THe question was related to v2 patches
<qschulz>
and since we usually want v2/v3 etc... in their own threads, I don't think it's useful to us?
<ptsneves>
ahh so this might be the reason i caused a confusion with the patches.
<RP>
zeddii: great, thanks!
goliath has quit [Quit: SIGSEGV]
alimon has joined #yocto
xmn has joined #yocto
florian has quit [Ping timeout: 240 seconds]
paowz_ has quit [Ping timeout: 244 seconds]
paowz_ has joined #yocto
Schlumpf has quit [Quit: Client closed]
gs1234 has joined #yocto
mckoan is now known as mckoan|away
frieder has quit [Remote host closed the connection]
ptsneves has quit [Ping timeout: 252 seconds]
rfuentess has quit [Ping timeout: 240 seconds]
rfuentess has joined #yocto
rfuentess has quit [Remote host closed the connection]
ruslan has joined #yocto
<ruslan>
How to install sysctl in Yocto image? What does provide it?
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
roussinm has joined #yocto
<roussinm>
--without-local-prefix in gcc-configure-common, doesn't seems to do what it's suppose to do, at least for nativesdk-gcc it doesn't remove the /usr/local/include from the searched path.
florian has quit [Ping timeout: 256 seconds]
JaMa has quit [Read error: Connection reset by peer]
JaMa has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<v0n>
hi there -- how do you usually set systemd services to be run as a specific user? Do you usually append the recipe to provide your own service unit file? Or do you add drop-ins in a user package?
nemik has quit [Ping timeout: 276 seconds]
nemik has joined #yocto
<v0n>
or do you run the service as the user somehow?
florian has joined #yocto
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
sakoman has quit [Quit: Leaving.]
sakoman has joined #yocto
<RP>
zeddii: perf fix seems to be holding, thanks! Of course I broke lttng-modules debug symbols containing buildpaths now :/
<RP>
zeddii: not sure how our normal builds aren't detecting that, bit worrying really
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
<RP>
zeddii: ah, it works on x86, just not anywhere else
mvlad has quit [Remote host closed the connection]
florian has quit [Ping timeout: 256 seconds]
goliath has quit [Quit: SIGSEGV]
vladest has joined #yocto
jpuhlman_ has joined #yocto
jpuhlman is now known as Guest3505
jpuhlman_ is now known as jpuhlman
Guest3505 has quit [Ping timeout: 276 seconds]
mrpelotaz0 has quit [Quit: Hasta la vista!]
mrpelotazo has joined #yocto
foxxesStar has quit [Ping timeout: 246 seconds]
sakoman has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 240 seconds]
nemik has joined #yocto
foxxesStar has joined #yocto
chep has quit [Read error: Connection reset by peer]