LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #yocto
Circuitsoft has quit [Quit: Connection closed for inactivity]
Entei[m] has joined #yocto
sakoman has quit [Quit: Leaving.]
starblue3 has quit [Ping timeout: 240 seconds]
starblue3 has joined #yocto
marinaro has joined #yocto
sakoman has joined #yocto
TundraMan has joined #yocto
marka has quit [Ping timeout: 260 seconds]
jclsn has quit [Ping timeout: 240 seconds]
jclsn has joined #yocto
pabigot has quit [Ping timeout: 245 seconds]
pabigot has joined #yocto
pabigot has quit [Ping timeout: 245 seconds]
pabigot has joined #yocto
amitk has joined #yocto
wooosaiiii has quit [Quit: wooosaiiii]
wooosaiiii has joined #yocto
sakoman has quit [Quit: Leaving.]
pabigot has quit [Ping timeout: 245 seconds]
pabigot has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
alessioigor has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
Guest98 has joined #yocto
<mischief> RP: i'm back at it... this seems like an SELinux issue, which i have 0 experience with :-(
<mischief> if i remove "--xattrs --xattrs-include='*'" from the copytree command, all is good
<mischief> strace reveals that we are setting the SELinux xattrs right before the EPERM from tar..
<mischief> 28579 mknodat(3, "./bootstrap", 0555) = 0
<mischief> 28579 setxattr("/proc/self/fd/3/./bootstrap", "security.selinux", "system_u:object_r:var_lib_t:s0", 31, 0) = 0
<mischief> 28579 openat(3, "./bootstrap", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK|O_CLOEXEC, 0555) = -1 EACCES (Permission denied)
adrianf has joined #yocto
Guest98 has quit [Quit: Client closed]
manuel1985 has joined #yocto
rob_w has joined #yocto
tgamblin has quit [Remote host closed the connection]
tgamblin has joined #yocto
mckoan|away is now known as mckoan
<mckoan> good morning
pabigot has quit [Ping timeout: 250 seconds]
Thorn_ has joined #yocto
Thorn has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
pabigot has joined #yocto
wooosaiiii has quit [Quit: wooosaiiii]
wooosaiiii has joined #yocto
rfuentess has joined #yocto
barometz has quit [Quit: you can't fire me!]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
barometz has joined #yocto
Kubu_work has joined #yocto
gsalazar has joined #yocto
Guest98 has joined #yocto
<Guest98> hi, morning everyone.
<Guest98> i have TARGET_LDFLAGS += "..." definitions in myrecipe.bb. i want to export this definition as target_link_libraries(exe ${TARGET_LDFLAGS}) in CMakeListst.txt, how can i do it? if i can't do this, i have to manually add all the definitions in TARGET_LDFLAGS to target_link_libraries and delete them from the recipe as well.
vladest has quit [Ping timeout: 240 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
amitk_ has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
ptsneves has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
<LetoThe2nd> yo dudX
<Guest98> hi
florian_kc has joined #yocto
<RP> mischief: Ah. Is this under pseudo? I think pseudo may need to learn some "magic" to help with security attributes :/
ptsneves has quit [Ping timeout: 246 seconds]
<mischief> RP: sigh, no
<mischief> it's a stupid tar bug.
<RP> mischief: ah, right, yes. I'm paging in context! Did ubuntu patch that?
vladest has joined #yocto
<mischief> i do not know, let me check the ubuntu sources i guess
vladest has quit [Client Quit]
vladest has joined #yocto
<mischief> based on my reading of whats in https://git.launchpad.net/ubuntu/+source/tar/, no
<mischief> i don't like it but i think i am going to just have to build tar from source in our yocto container
xtopher__ has quit [Ping timeout: 246 seconds]
xtopher__ has joined #yocto
ndec has quit [Ping timeout: 246 seconds]
ndec has joined #yocto
Crofton has quit [Ping timeout: 246 seconds]
Crofton has joined #yocto
<Guest98> im trying to pass TARGET_LDFLAGS += "..."  to CMakeLists like that :
<Guest98> EXTRA_OECMAKE += "-DTARGET_LDFLAGS=${TARGET_LDFLAGS}"
<RP> mischief: buildtools tarball didn't help? Perhaps we should be adding a patch from tar upstream and rebuilding?
<Guest98> as far as i read,  i can export the variable in this way. but im getting error. any idea?
leon-anavi has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
xmn has quit [Ping timeout: 260 seconds]
<mischief> RP: buildtools is built by yocto itself right? with the yocto metadata?
<mischief> this release of tar is from 2 years ago and does not contain the patch.
xmn has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
ptsneves has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
manuel1985 has quit [Remote host closed the connection]
florian_kc has quit [Read error: Connection reset by peer]
manuel1985 has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
<RP> mischief: correct
prabhakarlad has joined #yocto
static_rocket has quit [Remote host closed the connection]
<Alban[m]1> rburton: Regarding the useradd dependency problem, I just noticed that appending to USERADDSETSCENEDEPS didn't work because there is a class-target override on this variable. Now using USERADDSETSCENEDEPS:append:class-target I can see that the do_package_setscene task do have the extra dependency. But I'm still unsure which dependency I should add to get the pulseaudio group. I used pulseaudio:do_populate_sysroot_setscene because other
<Alban[m]1> dependencies in USERADDSETSCENEDEPS use this task as well, but I have no idea what this task does.
amitk_ has quit [Ping timeout: 246 seconds]
<mischief> RP: so.. buildtools can't help me in that case unfortunately
<mischief> and unfortunately ubuntu 18 has too old gettext to build HEAD of tar so now i have to fix that too :)
xmn has quit [Quit: ZZZzzz…]
<RP> mischief: I was meaning we might consider adding that patch as a backport so the next buildtools would have it. You could also patch tar locally and build a new buildtools?
<RP> ("bitbake buildtools-tarball")
<mischief> i have to get that new buildtools into the build container somehow though
<mischief> we need to upgrade from ubuntu 18 to 22 anyway; since ubuntu 18 is sorta EOL'd and ubuntu 22 has a new coccinelle :)
amitk_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
amsobr has quit [Quit: Konversation terminated!]
<mischief> RP: is there some kind of automation the yocto project uses that could exercise this? testing oe.path.copytree or archiver.bbclass on a SELinux enabled host?
<RP> mischief: we don't have any selinux enabled hosts to test on
amitk_ has quit [Ping timeout: 245 seconds]
<mischief> i think fedora, alma linux and opensuse leap all support it and they are described as supported hosts for yocto. does nobody use those in the automation infrastructure?
zpfvo has quit [Ping timeout: 246 seconds]
kpo has quit [Ping timeout: 260 seconds]
amitk_ has joined #yocto
starblue3 has quit [Ping timeout: 245 seconds]
amitk_ has quit [Ping timeout: 245 seconds]
starblue3 has joined #yocto
zpfvo has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
amitk_ has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
Guest98 has quit [Quit: Client closed]
Guest98 has joined #yocto
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #yocto
arkanoid has quit [Ping timeout: 264 seconds]
amitk_ has quit [Ping timeout: 245 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
amitk_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
prabhakarlad has quit [Quit: Client closed]
<Guest98> when trying to build myproject on yocto with cmake, it cannot find string, iostream, vector, limits headers. could it be a problem with sysroot somehow? i handled my own .cpp and .hpp files. any idea?
<rburton> Guest98: sounds like your cmakelists is doing Bad Things
<mcfrisk> Guest98: not using cmake.bbclass and the toolchain file provided by it?
<rburton> because lots of cmake recipes work just fine
amitk_ has quit [Ping timeout: 246 seconds]
amitk_ has joined #yocto
amitk_ has quit [Ping timeout: 246 seconds]
ptsneves has quit [Ping timeout: 245 seconds]
<Guest98> rburton rookie doing rookie things. i shouldnt have override CMAKE_CXX_FLAGS, should have append.
<Guest98> i found a line like that:
<Guest98> set(CMAKE_CXX_FLAGS "-DOPENCV_ACTIVE -DRASPBERRYPI4 -O3 -Wall -fmessage-length=0 -pthread")
<Guest98> modify to:
<Guest98> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -DOPENCV_ACTIVE -DRASPBERRYPI4 -O3 -Wall -fmessage-length=0 -pthread")
<Guest98> problem solved, thanks. "cmakelists is doing Bad Things", it even helped me understand. :D
zpfvo has quit [Ping timeout: 245 seconds]
<rburton> yeah thats the sort of thing :)
ptsneves has joined #yocto
zpfvo has joined #yocto
xmn has joined #yocto
jetm- has quit [Quit: ZNC 1.7.2 - https://znc.in]
philmd- has quit [Quit: ZNC 1.7.2 - https://znc.in]
jetm- has joined #yocto
ptsneves1 has joined #yocto
rob_w has quit [Ping timeout: 246 seconds]
amitk_ has joined #yocto
philmd- has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
amitk_ has quit [Ping timeout: 245 seconds]
florian has joined #yocto
amitk_ has joined #yocto
marinaro has quit [Ping timeout: 245 seconds]
amitk_ has quit [Ping timeout: 252 seconds]
pbsds has quit [Quit: The Lounge - https://thelounge.chat]
florian has quit [Ping timeout: 246 seconds]
ptsneves1 has quit [Ping timeout: 246 seconds]
Guest41 has joined #yocto
<Guest41> Hi, I need to patch a file called "simple.script" that is in busybox local files. How to do it ? I can't use the method described here because this file is not in the sources so it can't be commited https://wiki.yoctoproject.org/wiki/TipsAndTricks/Patching_the_source_for_a_recipe
<Guest98> maybe u can add your "simple.script" file with .bbappend
<rburton> Guest41: in your layer have a bbappend for busybox, set FILESEXTRAPATHS, and then just put the modified simple.script in files/
prabhakarlad has joined #yocto
vladest has quit [Ping timeout: 245 seconds]
<rfs613> question regarding libraries built by yocto for use on the host (eg foobar-native packages)
<rfs613> builing openssl-native for example produces build/tmp/sysroots-components/x86_64/openssl-native/usr/lib/libcrypto.so.1.1
<rfs613> s/builing/building/
<rfs613> but when building curl-native, the binary links to libcurl.so from the sysroot, however it uses the host libcrypto, not the sysroot one.
Guest41 has quit [Ping timeout: 246 seconds]
<rfs613> i'm picking on curl just as an example here. Wondering in general, what determines if library from sysroot versus the build host gets used?
Xagen has joined #yocto
<sudip> rfs613: I went into a devshell and did a ldd on curl, it shows it has linked with libcrypto from recipe-sysroot-native
jetm- has quit [Quit: ZNC 1.7.2 - https://znc.in]
philmd- has quit [Quit: ZNC 1.7.2 - https://znc.in]
<sudip> khem: another example of devshell advantage :)
<rfs613> sudip: could you try using ldd without using devshell, and tell me which libcrypto it shows?
<sudip> without devshell it will just show you whatever libcrypto you have in your host,
vladest has joined #yocto
Guest98 has quit [Quit: Client closed]
vladest has quit [Read error: Connection reset by peer]
vladest has joined #yocto
<rfs613> hmm i don't see that here. But really I am trying to understand how it works. Is bitbake modfying LD_LIBRARY_PATH for example, or something similar?
sakoman has joined #yocto
<sudip> it will have its own LDFLAGS, but you can see more on what its doing in the run.do_compile script, for me its at tmp/work/x86_64-linux/curl-native/8.1.2-r0/temp/run.do_compile
jpanisbl has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
<rfs613> yes, I see it sets LDFLAGS to pass -L flag... also I see a wrapper script that prefixes to LD_LIBRARY_PATH
pabigot has quit [Ping timeout: 252 seconds]
jpanisbl has quit [Quit: Konversation terminated!]
zpfvo has joined #yocto
pabigot has joined #yocto
Kubu_work has quit [Ping timeout: 245 seconds]
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #yocto
<yudjinn[m]> running into a super confusing error. I have a job that should ONLY run when a large rebuild happens; I handled that by doing a check_breaking_change[depends] += " libgcc:do_compile ". Now, locally, this works as expected. but my CI uses SSTATE from an NFS mount, and this task runs (incorecctly) even when it doesnt need to rebuild that job. I can even go through the logs and see that libgcc only uses a setscene. I'm at a loss, as I've been
<yudjinn[m]> trying to resolve this for weeks
Kubu_work has joined #yocto
<rburton> yudjinn[m]: how do you define a large rebuild? how does that [depends] do what you want?
<yudjinn[m]> rburton: so I have a task in my image recipe that runs only when libgcc is recompiled. I basically want to have this run ONLY when it it fully recompiled (like changes were detected in libgcc). Otherwise, If it's just using the cached one (because I made a change in something downstream of libgcc), the task should not run. My understanding was that if bitbake detected no changes, it would run a `do_compile_setscene` instead of a `do_compile`
<yudjinn[m]> so the task wouldnt run
<yudjinn[m]> edit: it runs a do_package_setscene not do_compile_setscene; the do_compile task is nowhere in my log, but it still runs that task that depends on do_compileh
adrianf has quit [Quit: Leaving]
manuel1985 has quit [Ping timeout: 246 seconds]
<rburton> yudjinn[m]: do_compile vs do_compile_setscene is an internal thing and unrelated to what you're trying to do.
<rburton> the tasks form a graph and if sstate is present chunks can be removed, so an image from sstate will just do libgcc:write_package_rpm and skip out the actual compile
Kubu_work has quit [Ping timeout: 245 seconds]
adrianf has joined #yocto
<rburton> yudjinn[m]: whats the use case for 'run a task in an image if libgcc was rebuild in this build run'? what if libgcc was build in a previous build?
<rburton> like the user did bitbake zlib; bitbake theimage
mckoan has quit [Read error: Connection reset by peer]
Kubu_work has joined #yocto
mckoan has joined #yocto
<yudjinn[m]> rburton: so I provide swupdate images as well as rpm repos, but I manage whether or not an image can use one or the other based on if something "breaking" (I defined as libgcc) has occurred. So this is expected to happen if, say, we update gcc version/recipe -> causes bitbake recompile -> run this `check_breaking_change` task; else, anything downstream (say, networkmanager), wouldnt cause this task to run
<rburton> that sounds fragile and hard to actually detect
<yudjinn[m]> its more my attempt at saying "if you HAD to rebuild gcc, this SHOULD be set as a swupdate update, not an rpm".
<rburton> what if someone else builds libgcc and your image pulls the sstate
<yudjinn[m]> The only thing that has write access to that sstate is our master branch CI
<yudjinn[m]> this task is almost entirely for making sure that certain version strings are correctly updated by the time they hit our initial "smoke test" CI jobs. If it detects you changed something that causes a rebuild, namely you made a change that caused a recompile of libgcc over the master sstate, then it requires you also bump a version in that PR. Otherwise, if you correctly updated the version, it still runs that task, but the result is just
<yudjinn[m]> info saying "You did the right thing" rather than a bb.error
<rburton> personally, sounds like you're trying to embed too much process into the details of the build. whether or not libgcc happened to be rebuilt in _this bitbake invocation_ shouldn't be deciding logic. i'm presuming if the pipeline fails then the builds sstate is thrown away, right?
<yudjinn[m]> correct, but once it hits master, it is fully rebuilt and is the new "master"
<rburton> i suggest you rethink your process, not sure how you'd even be able to know that libgcc:do_compile happened in _this build in particular_ from another recipe, ignoring the details about how fragile that is and needs a very specific build/sstate setup
zpfvo has quit [Ping timeout: 245 seconds]
<rburton> i guess you could make libgcc:do_compile drop a file in the build tree somewhere and look for that, but i'm not sure how you'd be sure it wasn't a stale file (you could expect a clean build tree every run, but again, fragile)
<yudjinn[m]> what do you mean? If i made no change for an MR, it would setscene the entire image. If I made a change to a recipe that was downstream of libgcc, this specific task doesnt run. if its upstream -> causes a recompile due to dependency rebuild. If that happens, if version is correctly updated -> no error; else, error
<yudjinn[m]> but once that is merged, that becomes the new sstate. so new MRs just rerun the logic
<yudjinn[m]> and its "technically" not just gcc. we also have a task-depends of linux:do_compile; so as we change KConfigs, this also throws an error if we dont correctly set it as a breaking change in the FS.
rfuentess has quit [Remote host closed the connection]
florian has joined #yocto
zpfvo has joined #yocto
cperon has quit [Remote host closed the connection]
zpfvo has quit [Remote host closed the connection]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
mckoan is now known as mckoan|away
Kubu_work has quit [Quit: Leaving.]
pbsds has joined #yocto
alessioigor has quit [Quit: alessioigor]
ptsneves has quit [Ping timeout: 260 seconds]
amitk_ has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
amitk_ has quit [Remote host closed the connection]
gsalazar has quit [Ping timeout: 246 seconds]
tlwoerner has quit [Ping timeout: 246 seconds]
PhoenixMage has quit [Remote host closed the connection]
florian has quit [Ping timeout: 246 seconds]
tlwoerner has joined #yocto
manuel1985 has joined #yocto
prabhakarlad has quit [Quit: Client closed]
cb5r has joined #yocto
nerdboy has quit [Ping timeout: 246 seconds]
Thorn has joined #yocto
Thorn_ has quit [Ping timeout: 246 seconds]
amitk has quit [Ping timeout: 245 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
nerdboy has quit [Remote host closed the connection]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
Wouter0100670440 has quit [Quit: The Lounge - https://thelounge.chat]
Wouter0100670440 has joined #yocto
Minvera has joined #yocto
beneth has joined #yocto
<khem> sudip: doing ldd on a cross compiled package is iffy regardless, you might have different results in final rfs
<sudip> khem: yes, agreed. that was just to show <rfs613> the difference
leon-anavi has quit [Quit: Leaving]
Xagen has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
goliath has joined #yocto
adrianf has quit [Ping timeout: 260 seconds]
manuel1985 has quit [Ping timeout: 240 seconds]
Minvera has quit [Ping timeout: 246 seconds]
<mischief> RP: today i tried a slightly different approach that i think will work
<mischief> i wrote a tar wrapper in python that just removes any --xattr arguments :)