ndec changed the topic of #yocto to: "Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Join us or Speak at Yocto Project Summit (2022.05) May 17 - 19, more: https://yoctoproject.org/summit | Join the community: https://www.yoctoproject.org/community | IRC logs available at https://www.yoctoproject.org/irc/ | Having difficulty on the list or with someone on the list, contact YP community mgr ndec"
mrnuke has quit [Read error: Connection reset by peer]
mrnuke has joined #yocto
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
mrnuke has quit [Read error: Connection reset by peer]
ak77 has quit [Quit: No Ping reply in 180 seconds.]
ak77 has joined #yocto
mrnuke has joined #yocto
erbo_ has quit [Ping timeout: 260 seconds]
erbo has joined #yocto
sakoman has quit [Quit: Leaving.]
rber|res has joined #yocto
RobertBerger has quit [Ping timeout: 252 seconds]
mrnuke_ has joined #yocto
mrnuke has quit [Ping timeout: 240 seconds]
xmn has quit [Quit: ZZZzzz…]
xmn has joined #yocto
sakoman has joined #yocto
<khem> RP: just saw this on riscv32 https://errors.yoctoproject.org/Errors/Details/663200/ ☹️
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<khem> this worked ok so far. It seems related to 64bit atomics which are not implemented on rv32/arm5/mips
michaf has quit [Ping timeout: 264 seconds]
jmiehe1 has joined #yocto
seninha has quit [Remote host closed the connection]
jmiehe has quit [Ping timeout: 255 seconds]
jmiehe1 is now known as jmiehe
amitk has joined #yocto
odra has quit [Ping timeout: 245 seconds]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
michaf has joined #yocto
angman has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
sakoman has quit [Quit: Leaving.]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
qschulz has quit [Remote host closed the connection]
qschulz has joined #yocto
thomasd13 has joined #yocto
odra has joined #yocto
odra has quit [Client Quit]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
imuguruza has joined #yocto
alessioigor has joined #yocto
<RP> khem: that has probably never been built before by us!
<RP> khem: MAX_ATOMIC_WIDTH[riscv32] = "32"
goliath has joined #yocto
mckoan|away is now known as mckoan
<mckoan> good morning
hcg has joined #yocto
Sona has joined #yocto
alessioigor has quit [Quit: alessioigor]
<LetoThe2nd> yo dudX
ptsneves has joined #yocto
florian has joined #yocto
ptsneves has quit [Read error: Connection reset by peer]
ptsneves has joined #yocto
<rber|res> @LetoThe2nd: O I D A
<LetoThe2nd> rber|res: OOOOIIIIDAAAA!
Guest87 has quit [Quit: Ping timeout (120 seconds)]
<michaf> Bäm oida.
<qschulz> Xagen: this recipe, you use it in DEPENDS, RDEPENDS, IMAGE_INSTALL?
hcg has quit [Quit: Client closed]
hcg has joined #yocto
mihai has joined #yocto
leon-anavi has joined #yocto
starblue has joined #yocto
* mckoan hears voices from the Alps :-D
<LetoThe2nd> mckoan: cool, what do they say?
<mckoan> LetoThe2nd: is Oida a kind of Jodel ?
<LetoThe2nd> mckoan: hehe no, its the local accent of "old guy", essentially a kind of joking version of "dude!"
<michaf> Also the term was widely used by a youth/sub-culture in vienna called "Krocha". Not sure if this is still a thing in 2022.
<LetoThe2nd> yes, and the German "cool kids" often address each other with "Yo Alter", which is the same without the accent. So essentially two old dudes like rber|res and me offensively using it is pretty straightforward ironic.
<michaf> I believe the proper term is "Digga" nowadays. However, this does not add any value to the whole thing. Anyway, culture is meant to be embraced. :D
<michaf> We should get back to topic too.
<michaf> Before anyone complains. :)
<LetoThe2nd> yeah, lets build stuff. OIDA!
<michaf> I'm still struggling getting the proper SDL2 include paths using PKGCONFIG. It seems to be ignored. Any advice?
<LetoThe2nd> michaf: we're kinda context-sensitive here usually. if a technical discussion is going on it should not be interrupted, but silencing the channel to make it feel like a graveyard when there's nothing on-topic going on is also not exactly helpful for the greater community. in a nutshell: use common sense :-)
<michaf> I like that.
<LetoThe2nd> michaf: i saw the original thread but at least I personally think rburton said everything necessary. what about setting up a small tester project with cmake+sdl that uses the canonical forms of dependencies and building, and see if that works?
<michaf> Since I wrote the initial CMakeLists.txt myself, I don't see why there should be any difference. Also rburtons suggestion with PKGCONFIG did not work.
<michaf> I'm not feeling very good with the idea in creating an option that disables the automatic dependency downloading via CMake only for that purpose.
<michaf> I rather add or remove a source file from do_compile() if necessary. I wanna put the yocto layer to my GitHub anyway.
<LetoThe2nd> michaf: well but thats the core problem. you are introducing additional builds that are hidden to the outside
<LetoThe2nd> michaf: that is essentially also the reason why npm integration is so painful.
<LetoThe2nd> michaf: it becomes especially problematic when cross compiling, and those hidden dependencies don't do it correctly, or take assumptions.
mvlad has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
mvlad has quit [Client Quit]
mvlad has joined #yocto
manuel1985 has joined #yocto
<rburton> michaf: looks like PKG_CONFIG doesn't exist everywhere, my mistake. just use $(pkg-config ...)
<rburton> i have a branch somewhere which makes this more reliable...
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
manuel1985 has quit [Ping timeout: 252 seconds]
Guest4 has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
Guest4 has quit [Client Quit]
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
michaf has quit [Ping timeout: 268 seconds]
ptsneves has quit [Read error: Connection reset by peer]
ptsneves has joined #yocto
ptsneves1 has joined #yocto
jmiehe has quit [Ping timeout: 276 seconds]
ptsneves1 has quit [Read error: Connection reset by peer]
ptsneves has quit [Read error: Connection reset by peer]
ptsneves has joined #yocto
ptsneves has quit [Read error: Connection reset by peer]
ptsneves1 has joined #yocto
michaf has joined #yocto
<michaf> rburton: Thanks, this seems to work.
<michaf> Still a few include paths from other recipes I need to catch somehow though. :D
ptsneves1 is now known as ptsneves
ptsneves has quit [Client Quit]
ptsneves1 has joined #yocto
manuel1985 has joined #yocto
thomasd13 has quit [Ping timeout: 252 seconds]
ptsneves1 is now known as ptsneves
starblue has quit [Ping timeout: 244 seconds]
ptsneves has quit [Read error: Connection reset by peer]
ptsneves1 has joined #yocto
ptsneves1 has quit [Read error: Connection reset by peer]
ptsneves has joined #yocto
limitlessgreen[m has joined #yocto
starblue has joined #yocto
manuel1985 has quit [Ping timeout: 240 seconds]
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
starblue has quit [Ping timeout: 245 seconds]
seninha has joined #yocto
imuguruza has quit [Quit: Client closed]
GNUmoon2 has quit [Remote host closed the connection]
davidinux has quit [Ping timeout: 252 seconds]
GNUmoon2 has joined #yocto
prabhakarlad has quit [Quit: Client closed]
michaf has quit [Quit: WeeChat 2.8]
Sona has quit [Quit: Client closed]
angman has quit [Quit: Client closed]
starblue has joined #yocto
manuel1985 has joined #yocto
MarianS has joined #yocto
Guest76 has joined #yocto
<MarianS> Hi,
<MarianS> I need some help understanding how the journald.conf is created in dunfell.
<MarianS> On my system I upgraded from Yocto sumo to Yocto dunfell.
<MarianS> After the upgrade to Yocto dunfell I'm missing ForwardToSyslog=yes and RuntimeMaxUse=64M from journald.conf
<MarianS> I looked on recipes and:
<MarianS> Can you please help me understand why the ForwardToSyslog=yes and RuntimeMaxUse=64M are missing from journald.conf and how is the proper way to add them?
<MarianS> Regards,
<MarianS> Marian.
starblue has quit [Ping timeout: 245 seconds]
starblue has joined #yocto
florian has quit [Quit: Ex-Chat]
MarianS has quit [Quit: Client closed]
Guest76 has quit [Quit: Client closed]
camus has quit [Quit: camus]
MarianS has joined #yocto
starblue has quit [Ping timeout: 252 seconds]
hcg has quit [Quit: Client closed]
hcg has joined #yocto
<Saur[m]> MarianS: They are in `meta/recipes-core/systemd/systemd-conf/journald.conf` now.
starblue has joined #yocto
<mihai> MarianS: systemd-conf needs to be installed to get that file
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
prabhakarlad has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
florian has joined #yocto
kscherer has joined #yocto
nemik has quit [Ping timeout: 272 seconds]
nemik has joined #yocto
hcg has quit [Quit: Client closed]
manuel1985 has quit [Ping timeout: 244 seconds]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
hcg has joined #yocto
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
manuel1985 has joined #yocto
Wlad has joined #yocto
<Wlad> Hi everybody
<Wlad> I try to establish the boost library beast in yocto on gatesgarth branch
<Wlad> but I could not find that recipe anythere
sakoman has joined #yocto
<Wlad> yes
<rburton> it might predate the boost in gatesgarth, or need to be abled
<rburton> enabled
<Wlad> okay
<rburton> yes beast was added in 1.77
<rburton> gatesgarth has 1.74
<rburton> so you'll need to upgrade boost, or possibly easier is to write a recipe for just beast
<Wlad> thanks. that save my day
<ptsneves> has anybody had the issue of flex putting #line <linenum> <file> where file is a TMPDIR path?
<ptsneves> my grep foo is not coming up with anything
<rburton> the issue where it's a build path?
<rburton> or where it puts them at all and you don't want them?
brazuca has joined #yocto
<MarianS> Thanksm, mihai, somehow is installed under /lib/systemd/journald.conf.d/00-systemd-conf.conf and is working
<Saur[m]> MarianS: Just see `meta/recipes-core/systemd/systemd-conf_1.0.bb`
<ptsneves> rburton: Where it puts a build path
<ptsneves> #line 1 "/home/pneves/Projects/yocto-superproject/poky/build/tmp/work/core2-64-poky-linux/fluentbit/1.9.6-r0/build/src/record_accessor/ra_lex.c"
<rburton> That was actually on my list of things to look at today, as I just stopped libtool doing the same for its generated files.
<rburton> Not entirely sure the best solution here. Full paths are good for the build as then you get proper errors, but we don't want full paths in the -src package really
<rburton> if flex support path remaping that would be good
<ptsneves> that is strange. So do you think it is a new behavior? I see it from files generated through cmake
<ptsneves> it does not look like it does.
<rburton> i expect you'll find that currently a lot of the paths will be relative
<MarianS> yes Saur[m]\, makes sense, but how the journald is reading /etc/systemd/journald.conf and /lib/systemd/journald.conf.d/00-systemd-conf.conf. Or is using only /lib/systemd/journald.conf.d/00-systemd-conf.conf?
goliath has quit [Quit: SIGSEGV]
gsalazar has joined #yocto
<ptsneves> @rburton but what is the gain in getting build host abs paths?
<ptsneves> it is my case
<Saur[m]> MarianS: Well, that is a question for systemd, but if I am not mistaken it will automatically add the contents of any files in `/lib/systemd/journald.conf.d` as if they were part of `/etc/systemd/journald.conf`. That way it is easy to add configuration file fragments without having to rewrite the entire configuration file.
<rburton> ptsneves: little gain
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<rburton> guessing its your cmake's flex invocation that is passing absolute paths, so flex does what it is told
<ptsneves> @rburton that is useful info. I never had much hands on with flex. Looking at flex source code i find it is itself generated...turtles all the way down
<rburton> flex is built with flex
<ptsneves> yeah i just got that revelation :D So it needs to be in host tools for us (do not remember a flex-initial)
<rburton> flex can bootstrap itself
<ptsneves> ohh cool. OK i just confirmed in the code that void set_input_file( char *file ) which sets the filename for the #line is taken straight from argc
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<rburton> (see how flex builds a stage1flexq
<rburton> q
<rburton> damnit focus
jmiehe has joined #yocto
<ptsneves> rburton: vim?
<ptsneves> :D
<rburton> less
<ptsneves> damn even using https://cmake.org/cmake/help/latest/policy/CMP0098.html#policy:CMP0098 and removing the CMAKE_CURRENT_BINARY_DIR i get the absolute path
<ptsneves> oh well hopefully somewhere here https://github.com/Kitware/CMake/blob/master/Modules/FindFLEX.cmake is the the right code path to get flex invoked with a relative path.
ptsneves has quit [Ping timeout: 245 seconds]
kanavin has quit [Quit: Leaving]
brazuca has quit [Quit: Client closed]
brazuca has joined #yocto
goliath has joined #yocto
Wlad has left #yocto [#yocto]
Estrella_ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
brazuca has quit [Quit: Client closed]
Guest1466 has joined #yocto
Guest1466 is now known as brazuca
GNUmoon2 has quit [Remote host closed the connection]
GNUmoon2 has joined #yocto
gsalazar has quit [Read error: Connection reset by peer]
gsalazar has joined #yocto
Estrella_ has joined #yocto
Estrella__ has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
goliath has quit [Quit: SIGSEGV]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
florian has quit [Ping timeout: 252 seconds]
rsalveti has quit [Quit: Connection closed for inactivity]
nemik has quit [Ping timeout: 255 seconds]
nemik has joined #yocto
goliath has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
mborzecki has joined #yocto
Estrella__ has joined #yocto
amitk has quit [Ping timeout: 252 seconds]
florian has joined #yocto
prabhakarlad has quit [Quit: Client closed]
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
goliath has quit [Quit: SIGSEGV]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
brazuca has quit [Quit: Client closed]
brazuca has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
MarianS has quit [Quit: Client closed]
prabhakarlad has joined #yocto
florian has quit [Ping timeout: 252 seconds]
seninha has quit [Ping timeout: 245 seconds]
gsalazar has quit [Ping timeout: 268 seconds]
brazuca has quit [Quit: Client closed]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
leon-anavi has quit [Quit: Leaving]
florian has joined #yocto
hcg has quit [Quit: Client closed]
jmiehe has quit [Ping timeout: 244 seconds]
Ram-Z has quit [Ping timeout: 245 seconds]
brazuca has joined #yocto
seninha has joined #yocto
<JaMa> khem: do you have your 2.36 WIP recipes for glibc somewhere public? I would test that DEBUG_BUILD issue there
<JaMa> khem: there is no fix mentioned in https://sourceware.org/bugzilla/show_bug.cgi?id=29249 and I haven't found anything in latest git repo, but still doing a build might be useful
prabhakarlad has quit [Quit: Client closed]
starblue has quit [Ping timeout: 245 seconds]
kanavin has joined #yocto
goliath has joined #yocto
Ram-Z has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
hcg has joined #yocto
Starfoxxes has quit [Ping timeout: 276 seconds]
kscherer has quit [Quit: Konversation terminated!]
kscherer has joined #yocto
kscherer has quit [Client Quit]
florian has quit [Ping timeout: 252 seconds]
Starfoxxes has joined #yocto
mvlad has quit [Remote host closed the connection]
<static_rocket> Hey lads, any advice for managing the yocto layers? I've seen some articles promoting submodules/subtrees/git-repo/kas/gr but it feels like I'm overlooking something...
<rburton> I like kas
<JPEW> static_rocket: They all have strengths and weaknesses. It just depends on what your requirements are
florian has joined #yocto
jmiehe has joined #yocto
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
florian has quit [Ping timeout: 244 seconds]
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 245 seconds]
nemik has joined #yocto
ardo has quit [Read error: Connection reset by peer]
ardo has joined #yocto
ardo has quit [Read error: Connection reset by peer]
alimon has quit [Remote host closed the connection]
ardo has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
goliath has quit [Quit: SIGSEGV]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
dtometzki has quit [Ping timeout: 272 seconds]
dtometzki has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
GNUmoon2 has quit [Ping timeout: 268 seconds]
sakoman has quit [Quit: Leaving.]