Wednesday, 2021-09-15

*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)00:14
*** qschulz <qschulz!> has quit IRC (Quit: qschulz)00:32
*** qschulz <qschulz!> has joined #yocto00:34
*** jwillikers <jwillikers!> has quit IRC (Remote host closed the connection)00:39
*** Johnsv <Johnsv!> has quit IRC (Quit: Ping timeout (120 seconds))00:43
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)00:44
*** Net147 <Net147!> has joined #yocto00:47
*** Ad0 <Ad0!~Ad0@> has quit IRC (Ping timeout: 252 seconds)01:03
*** OutBackDingo <OutBackDingo!~quassel@> has quit IRC (Quit: - Chat comfortably. Anywhere.)01:05
*** OutBackDingo <OutBackDingo!~quassel@> has joined #yocto01:06
*** Ad0 <Ad0!~Ad0@> has joined #yocto01:08
*** FredO <FredO!> has quit IRC (Quit: Leaving)01:12
yatesregarding sysroot population and the tmp/sysroots-components, what if a package reported in a task's "NOTE: Installed into sysroot:" log is under more than one subdirectory of tmp/sysroots-components?01:32
yatesor is that arranged so that it never happens? (looks like it)01:34
yatesand what is the tmp/sysroots-components/<some-foldr>/<some-sysroot-folder>/sysroot-providers used for? it looks like some "keyng" mechanism, but i don't quite get it01:35
yatesare most people east of the U.S.?01:37
moto-timoyates: we’re global, but historically a lot of folks have been EU01:45
moto-timoI’m pacific time zone01:46
yatesi see02:01
yatesstill early for you, then...02:01
moto-timoIf 7pm is early02:03
moto-timoTo me that’s 12+ hours into my day02:03
*** _whitelogger <_whitelogger!> has quit IRC (Remote host closed the connection)02:04
*** _whitelogger <_whitelogger!> has joined #yocto02:06
yatesi'm EST, and I started roughly the same time. but i've had lots of breaks...02:06
yatesthis "work-from-home" paradigm has made my schedule quite crazy!02:07
yatesand being 63 i can't seem to sleep a full 7 or 8 hours anymore..02:07
*** sakoman <sakoman!~steve@> has quit IRC (Quit: Leaving.)02:31
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)02:35
*** tlwoerner <tlwoerner!> has quit IRC (Ping timeout: 260 seconds)02:43
*** tlwoerner <tlwoerner!> has joined #yocto02:46
*** tlwoerner <tlwoerner!> has quit IRC (Client Quit)02:47
*** tlwoerner <tlwoerner!> has joined #yocto02:47
*** zpfvo <zpfvo!~fvo@> has quit IRC (Ping timeout: 265 seconds)02:55
*** zpfvo <zpfvo!~fvo@> has joined #yocto03:09
*** nsdrude[m] <nsdrude[m]!~nsdrudema@2001:470:69fc:105::f855> has joined #yocto03:31
*** nsdrude[m] is now known as hereiam[m]03:36
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 268 seconds)04:03
*** zeddiii <zeddiii!> has joined #yocto04:23
*** zeddii <zeddii!> has quit IRC (Ping timeout: 240 seconds)04:23
*** amitk <amitk!~amit@> has joined #yocto04:39
*** zeddiii <zeddiii!> has quit IRC (Ping timeout: 265 seconds)04:45
*** ThomasD13 <ThomasD13!> has joined #yocto05:12
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto05:48
*** agrue <agrue!> has quit IRC (Ping timeout: 268 seconds)06:03
*** agrue <agrue!> has joined #yocto06:06
*** tre <tre!> has joined #yocto06:11
JosefHolzmayr[m]yo dudX06:46
*** Tyaku <Tyaku!> has joined #yocto06:51
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:56
*** frieder <frieder!> has joined #yocto06:58
*** mckoan|away is now known as mckoan07:04
mckoangood morning07:04
*** rfuentess <rfuentess!~rfuentess@2a01:598:89f5:9963:d51:e2fa:404c:e241> has joined #yocto07:09
JosefHolzmayr[m]any pointers on how to actually get the public sstate mirror to kick in? i'm tinkering around for demonstration purposes, and even on a completely unmodified dunfell build, not a single hit appears.07:10
*** Guest27 <Guest27!~Guest27@> has joined #yocto07:13
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Quit: WeeChat 3.1)07:17
JosefHolzmayr[m]even when checking out the 3.1.10 tag and setting the path accordingly, i get found 3 - missed 114807:19
RPJosefHolzmayr[m]: You need master with that variable I mentioned07:19
JosefHolzmayr[m]RP: you mentioned something? where?07:20
RPJosefHolzmayr[m]: It doesn't work with dunfell as there is no read only hash equivalence data to match (except there is no, it just can't work with dunfell)+07:23
JosefHolzmayr[m]RP: ah missed that one. my bad. so this essentially means that after the hashequiv server has been turned on, all prior usecases have been invalidated. correct?07:24
*** manuel1985 <manuel1985!~manuel198@> has joined #yocto07:26
RPJosefHolzmayr[m]: since we enabled it, it did stop sstate working from the AB until we had this as well07:27
JosefHolzmayr[m]RP:  okay, i think i got it. just trying to understand the current situation (as i can't show/tell/explain things that i don't at least have a basic grasp of myself)07:29
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto07:36
*** xmn <xmn!> has quit IRC (Quit: ZZZzzz…)07:37
*** gsalazar <gsalazar!~gsalazar@> has quit IRC (Read error: Connection reset by peer)07:37
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto07:37
JosefHolzmayr[m]RP: it seems to work now, thanks.07:38
RPJosefHolzmayr[m]: np, trying to help :)07:45
*** prabhakarlad <prabhakarlad!> has joined #yocto07:52
JosefHolzmayr[m]13 minutes core core-image-minimal. not bad.07:55
mckoanJosefHolzmayr[m]: sounds great. Are you going to discuss it in the next Twitch?08:07
JosefHolzmayr[m]mckoan: don't think so08:08
TyakuHi, I come again about my libraries issues. I have a recipe A that provide a static library (.a) and header files. (The header files appear in workdir/sysroot-destdir/usr/include/matter and library in workdir/sysroot-destdir/usr/lib). The recipe B arrive to build using the library of recipe A, but now my problem is when i set "#include 'file'" in the sources of recipe B) "No such file or directory".08:09
TyakuOn the CMake project of recipe B, i have include directories set as "/usr/include/matter"08:10
qschulzTyaku: I assume the CFLAGS/LDFLAGS/CXXFLAGS/CPPFLAGS/whatever that are passed by Yocto aren't used in your cmake or overridden by it08:10
TyakuAnd during the build, I see the "-I/usr/include/matter"08:11
qschulzTyaku: yeah, that's most likely incorrect08:11
TyakuBut I think it search on "computer" paths (not sure).08:11
qschulzyup looks like it08:11
TyakuSo the correct way is not to define the include directories in the CMakeList.txt, but in the recipe ?08:12
TyakuWith the variables that you said08:12
qschulzuse whatever the build system is giving you08:13
JosefHolzmayr[m]Tyaku: the key is to not have the include pathes absolute, but having them automatically determined so that the outer build environment can adjust them as needed.08:13
olani[m]Or use -I=/usr/include/matter if you have to do it like that.  The = is replaced with whatever is given to gcc as sysroot and ignored otherwise.  I would not recommend it as the preferred solution, but it works.08:18
JosefHolzmayr[m]olani: interesting "dirty" trick, but agreed, absolutely not recommened, at least not without extensive comments explaining it.08:19
TyakuCurrently during the build it use -I/usr/include/matter and it still don't find the files, but as qschulz said, i think it search on "host computer" directories instead of the "/usr/include/matter" in Yocto dirs08:19
olani[m]Josef Holzmayr (TheYoctoJester): Sometimes you have makefiles that have to work in several build environments and pkg-config is not available.08:20
TyakuI looking how to do it properly, I found some examples but i'm looking for examples base on CMake Project08:20
JosefHolzmayr[m]olani: yeah i completely agree. but the '=' character is so hard notice and so little revealing in itself that i would request the maintainer to have an extensive comment right next to it, if the process actually depends on this behaviour.08:22
mckoanJosefHolzmayr[m]: therefore would you mind sharing the local.conf you used to test it ?08:23
*** camus1 <camus1!~Instantbi@> has joined #yocto08:23
olani[m]Tyaku: The "correct" way would be to install a pkg-config file from recipe A and use whatever CMake uses to read such files to find the correct paths.08:24
*** camus <camus!~Instantbi@> has quit IRC (Quit: camus)08:24
*** camus1 is now known as camus08:24
mckoanJosefHolzmayr[m]: thank you08:28
Tyakuolani[m] Jesus, it's terrible, when I search on internet I don't find examples about these basic things: A recipe that build using a library + headers from another recipe using CMake.08:31
olani[m]Tyaku I'm afraid I do not know CMake, but both consumes and generates pkg-config files (.pc)08:38
olani[m]and has a recipe in meta-openembedded08:39
JosefHolzmayr[m]yeah the main source for your headaches is probably that you wrangling two sides in one. i' suggest to first make a recipe that uses some random, already existing library. and then, in a second step, make a recipe that mimics the library behaviour with your own.08:41
*** florian <florian!> has joined #yocto08:50
*** bantu_ <bantu_!> has quit IRC (Quit: bantu_)08:54
*** bantu <bantu!> has joined #yocto08:54
*** kayterina <kayterina!> has joined #yocto08:55
RPkanavin: - another render node issue - at least it shows the error though!08:56
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Ping timeout: 268 seconds)08:59
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto09:01
TyakuDid someone know how to generate .pc files (for pkg-config) on yocto  ? The docs says: "The pkg-config class provides a standard way to get header and library information. This class aims to smooth integration of pkg-config into libraries that use it.09:21
TyakuDuring staging, BitBake installs pkg-config data into the sysroots/ directory. By making use of sysroot functionality within pkg-config, this class no longer has to manipulate the files."09:21
TyakuSo is it supposed to be automatic if we just inherit from pkgconfig ?09:22
olani[m]That inherit only ensures that the native pkg-config tool is available to your build.09:23
olani[m]Each package can generate pkg-config in its own build system.  Looking at libmusicbrainz that is done with CONFIGURE_FILE here
olani[m]The files should be installed to /usr/lib/pkgconfig.  If you do this right the pc file will be included in the sysroot for dependent recipes.09:26
TyakuMy first project is not CMake based, only the second that use the library :/09:26
RPkanavin: looks the same, maybe it is opensuse specific?09:28
olani[m]The pc file is not complicated, take something like and clean it up for your library.  Documentation for pkg-config starts here
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 252 seconds)09:29
olani[m]If I remember correctly you install some headers to /usr/include/matter and a static library to /usr/lib, then your pc file could look like... (full message at
olani[m]Going to libmusicbrainz again they use FIND_PACKAGE on line to find a cmake module(?) defined here that use pkg-config to read data from the libxml2.pc file.09:36
*** camus <camus!~Instantbi@> has joined #yocto09:36
TyakuSo, for the first step, I just have to put the .pc in the folder of my recipe where I put "external files / patches". Then just inherit "pkgconfig" and the job should be done ? I see the pkgconfig.bbclass and it seems to create the pkgconfig directory (but i'm not sure).09:45
olani[m]The pc file has to be installed to ${D}${libdir}/pkgconfig in recipe A.  It should then automagically be available in the sysroot of reciepe B.09:46
olani[m]You only need to inherit pkgconfig in recipe B09:47
TyakuIn workdir/image or workdir/sysroot-destdir I don't have the folder with pkgconfig file.09:47
olani[m]Which recipe?09:47
olani[m]If it is not in recipe A workdir/image you have not installed it correctly09:48
olani[m]pc-files are handled as header files in the way that they are not bitbake files but files that are part of the package build.09:49
Tyakuit is not supposed to be automatic if we inherit "pkgconfig.bbclass" ?
olani[m]Do you actually use that version:... (full message at
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto09:53
olani[m]The pkgconfig.bbclass file that I use do not install any pc-files09:53
TyakuNop, Let me check my local file ..09:54
TyakuI'm using hardknot, but i'm looking the content to see if it differs09:54
olani[m]I'm also on hardknott and my pkgconfig.bbclass is only a single line09:54
TyakuYep me too09:56
TyakuOk, so i'm going to manualy configure it.09:56
olani[m]I would do all of that in the project makefile.  Then you can also make sure that the paths in the pc file matches the paths where the headers and libs are installed.  GNU coding standards say (paraphrased) that pc-files should be generated at the install stage so they always match the values of $prefix and so on used at make install.09:58
rburtonTyaku: pkgconfig.bbclass simply pulls in a build dependency, it doesn't know (and cannot) know how to install pkgconfig files10:05
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:08
TyakuCurrently it didn't work during the build of recipe B, because find_package() is looking for .cmake files (different structure from .pc), after some research find_package() don't use the .pc files, we have to use pkg_check_modules() or pkg_search_module() instead. But as I understand the objective of this is *just* to set the includes/cflags/... as defined in the configuration file provided by Receipe A (the10:17
Tyakulibrary recipe). But for my initial problem, not sure it will change something because I had in my CMakeList the include directories configured to /usr/include/matter, The files I'm looking for exists in this (workdir/image and workdir/sysroot-destdir), during the build it was not finding the header file because I think it search on computer folder.10:17
*** coldspark29[m] <coldspark29[m]!~coldspar_@2001:470:69fc:105::db09> has joined #yocto10:28
*** mckoan is now known as mckoan|away10:31
TyakuWell... I find the correct include folder:  "-I${STAGING_DIR_TARGET}/${includedir}/matter"10:33
olani[m]Using pkgconfig files will help you with those paths. Or you can use the -I= flag I mentioned above.10:43
TyakuYep, But only if the .pc file use the correct directory (so not /usr/include/matter, but with ${STAGING_DIR_TARGET}). I think I will see how to integrate pkgconfig but later. Currently I focus on building a software that use a library.10:45
rburtonTyaku: what is the library you're building?10:53
TyakuThis is the CHIP library.10:53
TyakuMy recipe for the "CHIP" library is based on this one:
rburtonhilarious/tragic that a corporate sponsors library designed to be used everywhere is so tricky to build/integrate10:55
TyakuCurrently I think it's not their objective to make a library "easy to use".10:57
qschulzrburton: have you checked the companies in the alliance? I am not surprised.. AT ALL :)10:57
rburtonqschulz: one glorious day they'll catch up10:57
rburton(i'm not surprised *at all*10:57
TyakuThis library use the GN build system witch is not realy supported by yocto yet, so just for it, i had to pass by a gn.bbclass that a good guy made. (based on chromium in meta-browser but yeah)10:58
TyakuWhy GN build system ? That's the question, maybe because of Mr Google.10:58
rburtonits less how to build the actual stuff, it's more the integration after that11:02
rburtonit should be installing things like pkgconfig files, cmake files, something11:03
*** Guest27 <Guest27!~Guest27@> has quit IRC (Ping timeout: 256 seconds)11:09
*** xmn <xmn!> has joined #yocto11:14
*** Belsirk <Belsirk!> has joined #yocto11:14
*** Guest27 <Guest27!~Guest27@> has joined #yocto11:16
*** rfuentess <rfuentess!~rfuentess@2a01:598:89f5:9963:d51:e2fa:404c:e241> has quit IRC (Remote host closed the connection)11:17
*** Ad0 <Ad0!~Ad0@> has quit IRC (Ping timeout: 265 seconds)11:29
*** zeddii <zeddii!> has joined #yocto11:33
*** Ad0 <Ad0!~Ad0@> has joined #yocto11:35
*** jwillikers <jwillikers!> has joined #yocto11:40
*** jwillikers <jwillikers!> has quit IRC (Remote host closed the connection)11:43
*** jwillikers <jwillikers!> has joined #yocto11:48
TyakuIf my library from receipe A have a lot of directories for includes and i want to put their content in /usr/include/matter, is there a recursive syntaxt to create folder & install files ? I'm sure this is not the good way:
*** xmn <xmn!> has quit IRC (Ping timeout: 240 seconds)11:54
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 265 seconds)11:54
TyakuThe include folder need to keep the same hierarchy as the rest ..11:54
rburtonTyaku: doesnt matter have an install function for that11:55
TyakuMatter is not made to work with yocto directly.11:56
rburtonthis isn't yocto-specific11:57
qschulzTyaku: probably better to tweak the cmake of CHIP/matter/gn to install to the includedir of your choice11:57
rburtonsoftware being able to install is a fundamental thing11:57
TyakuAnd the only tutorial about building matter exemples/lib/.. for yocto are using the toolchain.11:57
rburtonok the building documentation has made me laugh/cry11:58
Tyakumatter/chip use GN. I can check how to do this11:58
rburtonthey appear to assume that you're building on-target, not installing, and just linking directly against the build tree11:58
rburtonwhich is frankly terrifying11:58
TyakuYes, the project is mainly "building from target" or you can cross-compile (in exemple folder)11:59
rburtonno wonder it has 1.6K issues11:59
rburtonthe shortcut for recursive install is mkdir -p. which creates all parents if needed.  ie mkdir ${D}${bindir} will make ${D}/usr before ${D}/usr/bin12:01
qschulzrburton: install -D does this too IIRC12:01
rburtonyeah, or that12:02
rburtonas this is terrible build infra i'd honestly say if it saves you time, cp -r and chown root:root afterwards.12:02
rburton(i'd normally say never do that)12:02
qschulzmmmm install -d does too: "treat all arguments as directory names; create all components of the specified directories"12:02
qschulzso whatever :p12:02
*** nerdboy <nerdboy!~nerdboy@> has joined #yocto12:07
olani[m]Tyaku: Your not supposed to need STAGING_DIR_TARGET in the pc file.  But maybe there is something in your package that defeats the OE setup.12:11
Tyakuolani[m]: Currently I don't use .pc file (i focussed on building my software, I will see this later). So currently in the recipe B I set TARGET_CFLAGS with -I${STAGING_DIR_TARGET}/${includedir}/matter12:14
TyakuJust for information, I succesfully arrived to build and helloword app, that use the library and some includes from recipe A (chip/matter) and call a function from this library to display some logs.12:15
olani[m]Tyaku: That's fine, I just thought you said you needed STAGINIg_DIR_TARGET in the pc file above.12:15
Tyaku[1616581530.038811][601:601] CHIP:-: TestingTask started!12:16
TyakuOk, But what I did is not good: 1. Because i only installed the includes from directories that i need to run the helloworld... 2. Because i have to do this install process directly in the recipe ... (as rburton remark, there is an issue to do it directly in CHIP GN Build system). 3. I don't use pkg-config.12:18
rburtonmatter doesn't set a pkgconfig file, so ignore that12:19
olani[m]Yeah, I did not realize that this was a package that was not your own. I'd say having install statements in the recipe is fine in this case.12:22
olani[m]Have you tried using #include <matter/header.h> instead of using -I flags?12:23
*** mihai- <mihai-!~mihai@user/mihai> has joined #yocto12:24
*** mihai- <mihai-!~mihai@user/mihai> has quit IRC (Remote host closed the connection)12:24
*** mihai <mihai!~mihai@user/mihai> has quit IRC (Read error: Connection reset by peer)12:25
*** bunk <bunk!~bunk@debian/bunk> has quit IRC (Ping timeout: 252 seconds)12:28
*** Guest27 <Guest27!~Guest27@> has quit IRC (Ping timeout: 256 seconds)12:28
Tyakuolani[m]: There is no such file, but in fact I put 4 include_directories because I don't control how the elements are included. In libCHIP.a, there are files where the #include start from "src" folder, sometimes it's from "lib" folder, sometimes it's from a generated folder [..]12:36
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto12:37
JosefHolzmayr[m]reminder, its less than an hour until ndec_ and me will be live for you at
*** vmeson <vmeson!> has joined #yocto12:38
*** tre <tre!> has quit IRC (Remote host closed the connection)12:40
olani[m]Tyaku: header.h was just an example. If you install the files to /usr/inlcude/matter it should be possible to #include them with matter/ prefix.  That way you get nice namespacing and do not need the -I-flag12:40
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto12:44
rburtonpersonally i'd be asking the matter support channels how you're meant to install it12:46
*** bunk <bunk!~bunk@debian/bunk> has joined #yocto12:56
*** bunk <bunk!~bunk@debian/bunk> has quit IRC (Client Quit)12:58
*** Tyaku <Tyaku!> has quit IRC (Quit: leaving)13:02
*** Tyaku <Tyaku!> has joined #yocto13:02
*** Tyaku <Tyaku!> has quit IRC (Client Quit)13:02
*** Tyaku <Tyaku!> has joined #yocto13:02
*** Tyaku <Tyaku!> has quit IRC (Client Quit)13:03
*** Tyaku <Tyaku!> has joined #yocto13:03
*** frieder <frieder!> has quit IRC (Ping timeout: 268 seconds)13:05
*** frieder <frieder!> has joined #yocto13:08
*** bunk <bunk!~bunk@debian/bunk> has joined #yocto13:10
user_123I have one question regarding usage of sharepoint/one drive in Yocto instead of ftp links13:10
user_123How to use share point sharepoint OR ondrive links in yocto13:11
user_123and store the supporting file for image build in these13:11
*** whuang0389 <whuang0389!> has joined #yocto13:12
ThomasD13Hi, maybe a dumb question: When I create my own machine configuration, is it possible to specify there the kernel which should be used? I would like to get away from all the kernel-recipes of my vendor TI13:20
TyakuAbout CHIP/Matter, I found that they have something related to pkg-config in their sources. I'm going to check, it's possible that the .py script build it13:26
qschulzThomasD13: yes,PREFERRED_PROVIDER_virtual/kernel = "<linux-recipe>" and/or PREFERRED_VERSION_virtual/kernel = "<linux-recipe-version>"13:27
JPEWWe are seeing a problem where a packagegroup doesn't rebuild when a package it pulls in bumps major versions; this causes it to look for the old library version when restored from sstate (e.g. libfoo0 when the new one is libfoo1) and causes a build failure. Does this sound famililar?13:29
JPEWIt seems like it might have been fixed in a more recent version of Yocto and I'd like to backport the fix but I cannot seem to find it13:30
ThomasD13thanks qschulz! A second question: The vendor add a lot of patches and config fragments for their kernel version. Can I somehow prevent the application of these patches via my own (maybe with higher priority) layer? Is that a "clean" way to do it?13:30
*** dmoseley <dmoseley!~dmoseley@> has quit IRC (Quit: ZNC 1.8.2 -
manuel1985Hello all. I intend to runqemu with kernel parameters supplied using bootparams=. Then I have systemd service which starts the ptest tests when the condition is fulfilled. Basically, on my devmachine I want to do a "kas shell -c runqemu bootparams=runtests kas-config.yml" and have qemu boot up and run the tests.13:37
manuel1985What are your opinions? Are there better ways to do this?13:37
manuel1985Is there existing functionality I can leverage?13:37
*** vd <vd!> has quit IRC (Quit: Client closed)13:44
qschulzThomasD13: if you use a differnet kernel recipe, the patches and config fragments won't apply to your new recipe13:44
qschulzThomasD13: if we're talking about vendor-kernel-specific changes to non-kernel recipes, I think you better start from scratch and ditch your vendor layer and start your own :)13:45
TyakuI'm watching webbinar :)13:48
tlwoernerwow, this is pretty stupid. i'm trying to register for ndec_ and JosefHolzmayr[m] talk, but because my company's name isn't in their preset dropdown list, it won't let me register13:49
*** vd <vd!> has joined #yocto13:49
tlwoernerso in order to register i'll have to pick a name of a company that i don't actually work for, one that's in their prepopulated list13:50
tlwoerneri chose "yocto project" ;-)13:51
*** gsalazar_ <gsalazar_!~gsalazar@> has joined #yocto13:51
*** gsalazar <gsalazar!~gsalazar@> has quit IRC (Ping timeout: 252 seconds)13:54
ndec_tlwoerner: heh..13:54
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto14:06
*** sakoman <sakoman!~steve@> has joined #yocto14:11
ThomasD13qschulz, thanks, I have to think about it. Not sure which mess is less :)14:12
qschulzThomasD13: it all depends how much you need from the vendor BSP layer. Usually it's machine conf file, kernel, and bootloader stuff. Those you can manually import in your own layer14:16
*** ThomasD13 <ThomasD13!> has quit IRC (Ping timeout: 252 seconds)14:17
*** fray <fray!~fray@> has quit IRC (Ping timeout: 265 seconds)14:20
*** fray <fray!~fray@> has joined #yocto14:21
*** koty0f <koty0f!> has joined #yocto14:25
*** dmoseley <dmoseley!~dmoseley@> has quit IRC (Quit: ZNC 1.8.2 -
*** koty0f_ <koty0f_!~filip@> has joined #yocto14:31
*** koty0f <koty0f!> has quit IRC (Ping timeout: 252 seconds)14:32
*** koty0f_ <koty0f_!~filip@> has quit IRC (Client Quit)14:34
*** koty0f_ <koty0f_!~filip@> has joined #yocto14:34
*** koty0f_ is now known as koty0f14:34
*** koty0f <koty0f!~filip@> has quit IRC (Client Quit)14:34
*** koty0f <koty0f!~filip@> has joined #yocto14:34
*** fray <fray!~fray@> has quit IRC (Ping timeout: 252 seconds)14:39
*** fray <fray!~fray@> has joined #yocto14:39
*** whuang0389 <whuang0389!> has quit IRC (Quit: Client closed)14:42
*** Tyaku <Tyaku!> has quit IRC (Quit: leaving)15:04
*** kayterina <kayterina!> has quit IRC (Remote host closed the connection)15:05
*** gsalazar_ is now known as gsalazar15:10
*** frieder <frieder!> has quit IRC (Ping timeout: 268 seconds)15:11
*** Belsirk <Belsirk!> has quit IRC (Remote host closed the connection)15:22
*** manuel1985 <manuel1985!~manuel198@> has quit IRC (Quit: Leaving)15:40
*** nerdboy <nerdboy!~nerdboy@gentoo/developer/nerdboy> has quit IRC (Ping timeout: 260 seconds)15:53
*** gsalazar <gsalazar!~gsalazar@> has quit IRC (Remote host closed the connection)15:54
*** gsalazar <gsalazar!~gsalazar@> has joined #yocto15:54
*** nerdboy <nerdboy!~nerdboy@> has joined #yocto16:07
*** koty0f <koty0f!~filip@> has quit IRC (Ping timeout: 268 seconds)16:09
*** zpfvo <zpfvo!~fvo@> has quit IRC (Remote host closed the connection)16:11
*** dev1990 <dev1990!~dev@> has joined #yocto16:33
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 252 seconds)16:34
*** florian <florian!> has quit IRC (Quit: Ex-Chat)16:36
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)16:37
*** behanw <behanw!> has joined #yocto16:46
*** vd <vd!> has quit IRC (Ping timeout: 256 seconds)16:46
*** gsalazar <gsalazar!~gsalazar@> has quit IRC (Ping timeout: 265 seconds)16:49
*** Guest53 <Guest53!~Guest53@> has joined #yocto16:50
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)17:00
RPDoes anyone fancy a reproducibility bug: ?17:27
*** bunk <bunk!~bunk@debian/bunk> has quit IRC (Quit: leaving)17:28
fraythe case on the right looks a lot like someone turned on the static user id code17:32
fraybut it's not on, one ht left17:32
* RP suspects an sstate hash issue with the static-group/passwd files from meta-selftest17:32
fraylol, there we go.. has static group/passwd seems odd17:33
RPfray: perhaps the task checksum isn't accounting for that being turned on17:33
fraymaybe, I hadn't thought of that..17:33
RPfray: the selftest static files use 522 as the number17:33
fraylooks like anon pthing is updating the configs.  So maybe this is hiding it from the hash processing17:37
fray'er.. anon python17:37
RPhmm, I'd expect the code to be able to see the result17:38
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)17:42
*** troth <troth!> has joined #yocto17:47
*** koty0f <koty0f!~filip@> has joined #yocto17:54
*** bunk <bunk!~bunk@debian/bunk> has joined #yocto18:21
*** vd <vd!> has joined #yocto18:25
vddo you usually find conf fragments in conf/include/* or does it have to be specific like conf/distro/include?18:29
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto18:29
RPvd: depends on the context18:31
*** mranostaj <mranostaj!~mranostaj@> has quit IRC (Ping timeout: 268 seconds)18:31
vdRP: I'm customizing the build, like adding OVERRIDES, changing IMAGE_LINK_NAME and a few other things based on BB_CURRENT_MC for various multiconfig. It is currently in the distro, but it doesn't feel right18:34
*** dmoseley <dmoseley!~dmoseley@> has quit IRC (Ping timeout: 260 seconds)18:36
RPvd: those do sound like distro things18:36
RPrburton, JPEW, sgw: Could someone have a look at and ack "create-spdx.bbclass: Search all license directories for license" please?18:37
vdRP: like setting IMAGE_LINK_NAME  "${IMAGE_BASENAME}" so that it's simpler to reference (and embed) an image into another. Where would you put such configuration? conf/distro/include/
vd(IMAGE_LINK_NAME = *)18:37
RPvd: it is part of your distro setup18:37
RPI mean you can put it where you like but it is really distro config18:38
vdok. I was a bit confused with the fact that image/machine/distro must be orthogonal, I felt like I couldn't easily test another distro like poky with my images, but I guess flexibility has its limits18:39
vdwhat I mean is that by referencing IMAGE_LINK_NAME (thus IMAGE_BASENAME) in my image recipes, they kinda become distro specific, but well you're right it's part of my distro anyway.18:41
RPvd: your images are probably strongly tied to your distro but as you say, at some point it isn't generic18:41
*** mranostaj <mranostaj!~mranostaj@> has joined #yocto18:41
vdespecially since they do require to inherit a few class, which makes them even less generic18:42
* vd says goodbye to core-image-minimal18:42
vdThe meaning of "distro" in OpenEmbedded is often a concern, I guess one must see it more as a "build" configuration in fact.18:44
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto18:45
RPdistro is the policy/configuration effectively18:45
*** dmoseley <dmoseley!~dmoseley@> has left #yocto18:47
RPkanavin: how are the deprecation fixes looking?18:47
vdso "ideally" image/distro/machine should be orthogonal, but it's rarely the case in the real world, right?18:47
JPEWvd: You can keep them pretty orthagonal... it can take a little work though18:50
RPvd: it definitely can be done, it likely just isn't worth it to you for your images18:50
vdok, thanks a lot.18:51
kergothI wouldn't go as far as to say it's rarely the case. Fairly common for new users to take shortcuts in that area until/if they realize the benefits of it, however18:58
*** dmoseley <dmoseley!~dmoseley@> has joined #yocto18:59
*** agrue <agrue!> has quit IRC (Quit: ZNC 1.7.5+deb4 -
*** agrue <agrue!> has joined #yocto19:09
JosefHolzmayr[m]RP: concerning the sstate thing from earlier - should qemu also be pulled?19:15
RPJosefHolzmayr[m]: depends if your configuration matches what the autobuilder builds19:17
JosefHolzmayr[m]RP: hmmm19:19
*** dmoseley_ <dmoseley_!~dmoseley@> has joined #yocto19:26
*** dmoseley_ <dmoseley_!~dmoseley@> has quit IRC (Client Quit)19:26
*** dmoseley_ <dmoseley_!~dmoseley@> has joined #yocto19:28
JosefHolzmayr[m]seems i missed the assume provided for libsdl219:29
*** dmoseley_ <dmoseley_!~dmoseley@> has quit IRC (Client Quit)19:30
*** manuel <manuel!~manuel@2a02:1748:dd5c:f290:c553:9012:6082:a89a> has joined #yocto19:32
manuelHi all! I'm creating an image for qemux86-64. When finishing the build, bitbake spends quite some time in do_image_tar. Is that necessary, when the image is only run in qemu?19:34
manuelI understand qemu accesses the .ext3 file19:34
*** manuel is now known as manuel198519:37
JosefHolzmayr[m]manuel: probably not exactly necessary.19:39
*** manuel1985 is now known as manuel19:39
JosefHolzmayr[m]what do you defined as "quite some time"?19:39
manuelA minute or so19:40
manuelCan I disable it?19:40
JosefHolzmayr[m]IMAGE_FSTYPES = "ext3" in local.conf to try. in the long run you might want to derive your own qemu version as MACHINE and set it there.19:41
*** koty0f <koty0f!~filip@> has quit IRC (Quit: Konversation terminated!)19:45
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto19:48
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)20:01
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto20:04
*** Starfoxxes <Starfoxxes!~Starfoxxe@2a02:8070:5390:d00:12bf:48ff:feb8:38c8> has joined #yocto20:16
*** dmoseley_ <dmoseley_!~dmoseley@> has joined #yocto20:27
*** dmoseley_ <dmoseley_!~dmoseley@> has quit IRC (Client Quit)20:27
*** florian <florian!> has joined #yocto20:35
*** vd <vd!> has quit IRC (Quit: Client closed)20:49
*** vd <vd!> has joined #yocto21:07
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)21:10
RPkergoth: an interesting dilemma: DESCRIPTION_abc = "Refer to ${DESCRIPTION}", OVERRIDES = "abc", getVar("DESCRIPTION")21:11
RPOnly "works" today since package.bbclass flattens variable references badly in emit_packagedata and I just tried to fix that21:12
*** alex88 <alex88!> has quit IRC (Ping timeout: 240 seconds)21:14
*** alex88_ <alex88_!> has joined #yocto21:14
*** amitk <amitk!~amit@> has joined #yocto21:17
vdmultiple overrides works, right? FOO_append_a_b is applied if and only if OVERRIDES contains both "a" and "b", correct?21:18
RPvd: yes21:21
* RP takes a wild guess that changing the way DESCRIPTION and SUMMARY work at M4 would not go down well21:21
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto21:22
ant__RP: IMAGE_FSTYPE...all is set in a random class...21:34
*** dmoseley_ <dmoseley_!~dmoseley@> has joined #yocto21:35
*** dmoseley_ <dmoseley_!~dmoseley@> has quit IRC (Client Quit)21:35
*** vd <vd!> has quit IRC (Quit: Client closed)21:36
ant__well, the original sinner was IMAGE_FSTYPES_collie :)21:37
RPfray: I think I found the issue for the user corruption and a fix that hopefully doesn't break too much else21:42
* RP sends a patch out21:46
frayexcellent.. I'll tkae a look21:48
*** bluearc <bluearc!~quassel@> has joined #yocto21:49
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 268 seconds)21:53
*** dmoseley_ <dmoseley_!~dmoseley@> has joined #yocto21:53
*** dmoseley_ <dmoseley_!~dmoseley@> has quit IRC (Client Quit)21:53
RPThe trouble was the pkgdata was identical for both dynamic and static cases with the recent do_package reproducibility improvements so it matched them up and accelerated the build with it21:53
*** dmoseley_ <dmoseley_!~dmoseley@> has joined #yocto21:59
*** dmoseley_ <dmoseley_!~dmoseley@> has quit IRC (Client Quit)21:59
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)22:01
frayYa,.. I can't say I completely undertand the fix, but I think I get the general idea..22:01
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has quit IRC (Quit: ZNC 1.8.2 -
*** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@> has joined #yocto22:10
*** Guest53 <Guest53!~Guest53@> has quit IRC (Quit: Client closed)22:19
*** yannd <yannd!~yann@> has joined #yocto22:19
*** otavio <otavio!> has quit IRC (Remote host closed the connection)22:29
*** jwillikers <jwillikers!> has quit IRC (Remote host closed the connection)22:41
*** prabhakarlad <prabhakarlad!> has quit IRC (Quit: Client closed)23:07
*** otavio <otavio!> has joined #yocto23:08
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has joined #yocto23:10
*** florian <florian!> has quit IRC (Ping timeout: 268 seconds)23:22
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)23:37
*** gioyik <gioyik!~gioyik@gateway/tor-sasl/gioyik> has quit IRC (Ping timeout: 276 seconds)23:39

Generated by 2.17.2 by Marius Gedminas - find it at!