<esai[m]>
hello everyone. I am looking for a AI project related with Image processing or Machine learning
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
leon-anavi has joined #yocto
<thomasd13>
Hi guys, I may need some help here: I wrote a recipe for a .net-application. At stage package-qa I got some errors for runtime dependency: https://dpaste.com/BQ9NK4MTB.txt
nemik has joined #yocto
<thomasd13>
It bascially requires libstdc++.so.6(GLIBCXX_3.4)(64bit) in different GLIBCXX versions. In my RDEPENDS I set libstdc++ as dependency like this: RDEPENDS_interprocesscommunication=" icu libgssapi-krb5 zlib libstdc++ "
<imuguruza>
Unfortunately, I am facing sox compilation error, it looks like autoconf is setting some commands not available, such as, arm...-gcc -qversion or -V, which it looks like they are deprecated or not supported anymore.
<imuguruza>
I have made a fresh compilation of that recipe in another computer (bitbake sox), and it compiles...
<imuguruza>
The cross-compiler version is the same. I am wondering what could the reason why in one compiles and in the other does not.
<imuguruza>
Any idea which can be the source of the problem? I have tried to clean the sox build using -c cleanall and cleansstate
<thomasd13>
I build against a AARCH64 target. Do you know maybe whats the issue here? I'm really surprised that it misses some kind of basic thing like the libstdc++
<bigendian>
hi. on kirkstone i am trying to compile a simple helloworld, similar to hello_1.0.bb
Guest12 has joined #yocto
<bigendian>
i get
<bigendian>
arm-poky-linux-gnueabi-gcc: not found
barometz has quit [Remote host closed the connection]
barometz has joined #yocto
Guest12 has quit [Quit: Client closed]
Schlumpf has joined #yocto
rfuentess has joined #yocto
imuguruza83 has joined #yocto
mckoan|away is now known as mckoan
<mckoan>
good morning
imuguruza83 has quit [Ping timeout: 252 seconds]
<sef>
morning
<Schlumpf>
morning
<thomasd13>
morning
prabhakarlad has joined #yocto
<sef>
(newbie question)
<sef>
hi, im trying to build opencv on imx. i want to build opencv_4.1.2.imx(zeus-5.4.3-1.0.0) instead of opencv 4.1.0 in "meta-openembedded".
<sef>
for this, i made the following definition in machine.conf: PREFERRED_VERSION_opencv ?= "4.1.2.imx"
<sef>
when i do "bitbake opencv", i get an error like this: "multiple .bb files are due to be built which each provide opencl-header"
<qschulz>
RP: working on Buildroot LTS CVEs for packages we use though, I'm not working on Yocto :/
goliath has quit [Quit: SIGSEGV]
<qschulz>
bigendian: can we see the recipe, source code of the sw you're building and the error log?
<qschulz>
thomasd13: this .NET application, it's using prebuilt binaries/shared libraries and not the ones built by Yocto right?
<bigendian>
qschulz: snipboardio/cYihFJ.jpg
<bigendian>
copied from poky meta-skeletons stuff
tre has joined #yocto
<bigendian>
tried as beaglebone-yocto machine but also qemux86-64
<bigendian>
just copied from hello_1.0.bb so supposing it was working
florian_kc has joined #yocto
<qschulz>
bigendian: that is one error I didn't expect to happen, no idea tbh
<bigendian>
qschulz: thanks anyway. So better i don0t show hello_1.0.bb in a seminar, or i am fired )
<qschulz>
bigendian: what I can say already is that we made a mistake, we shouldn't have hello_2.10.bb and hello_1.0.bb recipe, since the second won't be built because of its version being lower than the other one
<qschulz>
(meaning we probably didn't test it)
<qschulz>
I've started a build, let's see
florian_kc has quit [Ping timeout: 244 seconds]
sef41 has joined #yocto
sef has quit [Ping timeout: 252 seconds]
<bigendian>
qschulz: no worries, joking. thanks for the support
<qschulz>
well, providing broken examples should be one of our worries :)
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
<thomasd13>
qschulz, this .NET application is using prebuild binaries and shared libs which are not built by yocto, but it seems that some of that prebuild shared libs have runtime dependencies on specific version of libstdc++.so (libstdc++.so.6(GLIBCXX_3.4)(64bit))
<thomasd13>
Nevertheless I specified libstdc++ as runtime dependency, and checked this with bitbake dotnet-app -e | grep ^RDEPENDS
<qschulz>
thomasd13: poor thomas
<qschulz>
thomasd13: I used to patchelf the binaries/shlibs to specify the shlibs created by Yocto but that's something you need to maintain yourself then and it's not nice
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<qschulz>
thomasd13: any way to ask this project to rebuild with an SDK you create with your Yocto image?
<thomasd13>
qschulz, maybe a misunderstanding here: I build the dotnet-app with Yocto, based on meta-mono (and there dotnet-native). So Yocto uses the dotnet-SDK to compile/build the dotnet-app. But the shared objects within the dotnet-app are prebuild I think
<thomasd13>
I was wondering if I need to tell yocto that it should build and deploy that specific libstdc++.so, or should modify dotnet-app that it do not ask anymore for that specific libstdc++.so?
<qschulz>
thomasd13: sorry, no experience with .NET nor meta-mono :/
florian has joined #yocto
<thomasd13>
alright :) thanks anyway qschulz
<thomasd13>
But you may know how to build the specific libstdc++ lib?
<qschulz>
thomasd13: i'm not sure this is the way to go, I'd more look into making dotnet use the libs you're actually building with yocto
<thomasd13>
ok
sstiller has joined #yocto
goliath has joined #yocto
imuguruza89 has joined #yocto
imuguruza has quit [Quit: Client closed]
<RP>
qschulz: I sent that one last Tuesday
imuguruza has joined #yocto
imuguruza8996 has joined #yocto
imuguruza89 has quit [Ping timeout: 252 seconds]
ptsneves has joined #yocto
<ptsneves>
mckoan: for real. I really hope i can go in the next year
<qschulz>
RP: "sent"?
murych has joined #yocto
sef41 has quit [Ping timeout: 252 seconds]
<mckoan>
ptsneves: sure
<qschulz>
bigendian: working on master, will check with kirkstone but I expect it to work too.. maybe an issue with your local setup?
beneth has joined #yocto
murych has quit [Read error: Connection reset by peer]
davidinux has quit [Ping timeout: 265 seconds]
murych has joined #yocto
Tyaku has joined #yocto
Payam has joined #yocto
davidinux has joined #yocto
rfuentess has quit [Remote host closed the connection]
<Tyaku>
Hi, I have a recipe, where I want different "SRC_URI" depending on the machine. Currently I try to do this like this: SRC_URI_gateway-pu551_append = " file://xxxx_defconfig" and I have different "machines".
<Tyaku>
The problem is that during the build "MACHINE=gateway-pu551 bitbake my-image" I get errors during the fetch of my recipe because it try to find the files of the other machines
<RP>
qschulz: I reported it to them via email. I forwarded you what I sent
<qschulz>
Tyaku: just do what the stackoverflow suggested for the defconfig
<qschulz>
use the same filename and put it in a subdirectory named after the machine
<qschulz>
then a simple SRC_URI += "file://defconfig" will fetch the correct one for your machine
<qschulz>
Tyaku: also, remember that SRC_URI_gateway-pu551_append is the old syntax. If you're using honister or kirkstone, it should be SRC_URI_g:taway-pu551:append instead
<qschulz>
SRC_URI:gateway-pu551:append
ptsneves has joined #yocto
<qschulz>
and probably even more: SRC_URI:append:gateway-pu551
<Tyaku>
My files have different names,
<Tyaku>
And the problem is that i get an error like this "Fetcher failure: Unable to find file file://a-file-from-machine-a anywhere. The paths that were searched were:" when I am building for machine-b, and if I build for machine-a, I have the same error but for machine-b
<qschulz>
Tyaku: can you send the content of your recipe and the directory layout for where you put your files?
zpfvo has quit [Ping timeout: 252 seconds]
<Tyaku>
yep
davidinux has quit [Ping timeout: 265 seconds]
<qschulz>
RP: thx, will look at it once systemd-oomd stops killing thunderbird when yocto is compiling :D
<imuguruza>
aarch64-poky-linux-gcc: error: unrecognized command-line option '-qversion'; did you mean '--version'?
<Tyaku>
woooow ;D
<Tyaku>
The option -V is not known by " aarch64-poky-linux-gcc"
zpfvo has joined #yocto
<imuguruza>
yeah I understand that, but not why this his happening if I already compiled in another computer and I am based in the latest gatesgarth commit branch...
alessioigor has joined #yocto
<qschulz>
Tyaku: u-boot-imx/imx8mn-hub-mz-evk is not the same name for the directory as hub-mz-evk override so that's one thing
<qschulz>
for the rest, I think you need to check the content of the SRC_URI variable for each machine
<qschulz>
bitbake-getvar will tell you that
<Tyaku>
Probably because it depends on the version of the GCC being used, what appens if you call "aarch64-poky-linux-gcc -V" ? Did -V appears when calling "aarch64-poky-linux-gcc --help" ?
<imuguruza>
I ve tried that and fails
alessioigor has quit [Quit: alessioigor]
patersonc[m] has left #yocto [#yocto]
<imuguruza>
but, to my understanding, this shouldn't be properly configured in the conf process?
patersonc[m] has joined #yocto
florian_kc has joined #yocto
<qschulz>
bigendian: managed to build hello example from meta-skeleton for kirkstone too, so very likely something wrong in your setup?
camus has quit [Ping timeout: 268 seconds]
camus has joined #yocto
<qschulz>
RP: ah yes, I sent the same mail, hopefully they'll fix it at some point :)
Krutchek has quit [Quit: WeeChat 2.3]
<RP>
qschulz: hopefully :)
Zappan has joined #yocto
murych has quit [Read error: Connection reset by peer]
murych has joined #yocto
murych has quit [Client Quit]
mckoan is now known as mckoan|away
<RP>
qschulz: they do usually get there
d-s-e has joined #yocto
<imuguruza>
allright, I have added "DEPENDs = libtool" and now looks like is compiling
<ptsneves>
besides adding more ram, what tactics do people use to address high ram usage in the build? Is there any ram pressure mechanism?
zpfvo has quit [Ping timeout: 248 seconds]
sef has joined #yocto
zpfvo has joined #yocto
davidinux has quit [Ping timeout: 268 seconds]
davidinux has joined #yocto
<qschulz>
ptsneves: there's this new pressure stuff in master
<qschulz>
ptsneves: you can always limit the number of threads used
<qschulz>
ptsneves: also check if your high mem usage isn't happening during packaging, in which case you could lower the memory used by compression algorithms (xz, zstd, ... have variables for setting it)
<ptsneves>
qschulz: Thanks. When you mean threads you mean concurrent tasks or what is passed as the -j parameter?
<ptsneves>
The packaging tip is a good one :)
sef has quit [Quit: Client closed]
<qschulz>
ptsneves: you can control both
<qschulz>
PARALLEL_MAKE vs BB_NUMBER_THREADS on the global level
<ptsneves>
qschulz: indeed :) thanks
imuguruza has quit [Quit: Client closed]
<RP>
zeddii: I have a patch for perf in -next FWIW
imuguruza8996 has quit [Ping timeout: 252 seconds]
sef has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
ecdhe has quit [Ping timeout: 264 seconds]
ecdhe has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
Guest6026 has joined #yocto
karl has quit [Ping timeout: 255 seconds]
abelloni has quit [Ping timeout: 255 seconds]
tangofoxtrot has quit [Remote host closed the connection]
mlaga97 has quit [Quit: No Ping reply in 180 seconds.]
mrnuke_ has joined #yocto
Zappan has quit [Ping timeout: 265 seconds]
Telgareith has quit [Quit: Ping timeout (120 seconds)]
Lihis has quit [Ping timeout: 265 seconds]
manuel_ has joined #yocto
mlaga97_ has joined #yocto
beneth has quit [Ping timeout: 252 seconds]
rperier has quit [Ping timeout: 248 seconds]
<Guest6026>
CMake Error at CMakeLists.txt (find_library):
<Guest6026>
In the SDK, there are two sysroots. One core2-64-xx-linux. It contains libluajit-5.1.so
<sef>
sorry for sharing it for the 3rd time, it's the last time i'm sharing it.
apprehend3108[m] has joined #yocto
lrusak[m] has joined #yocto
nemik has quit [Ping timeout: 244 seconds]
khem has joined #yocto
patersonc[m] has joined #yocto
nemik has joined #yocto
kiwi_29_[m] has joined #yocto
Perceval[m] has joined #yocto
agherzan has joined #yocto
cperon has joined #yocto
kayterina[m] has joined #yocto
zyga[m] has joined #yocto
Alban[m] has joined #yocto
fabatera[m] has joined #yocto
ThomasRoos[m] has joined #yocto
NicoMller[m] has joined #yocto
jackos888[m] has joined #yocto
kmaincent[m] has joined #yocto
berton[m] has joined #yocto
mrybczyn[m] has joined #yocto
<LetoThe2nd>
sef: if i had to guess, then you're missing some PREFERRED_PROVIDER magic. but really, just guessing.
nemik has quit [Ping timeout: 248 seconds]
nemik has joined #yocto
gstinocher[m] has joined #yocto
simpat2022[m] has joined #yocto
Salamandar has joined #yocto
Tartarus has joined #yocto
yocti has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
T_UNIX[m] has joined #yocto
barath has joined #yocto
ericson2314 has joined #yocto
<qschulz>
could also be that some recipe somewhere actually use the direct name of a recipe instead of the virtual one
jordemort has joined #yocto
<qschulz>
e.g. you have recipe foo and recipe bar, both PROVIDES baz. One recipe bob (R)DEPENDS on bar, a recipe alice (R)DEPENDS on baz, but PREFERRED_PROVIDER_baz = "foo", so bitbake wants to build both foo and bar but both provide baz
majoribanksaud[m has joined #yocto
<manuel1985>
Offtopic question, hope that's okay here: Can anyone recommend me some tool to draw UML class and sequence diagrams? Installable on Debian if possible. Tried a few but they all felt hard to use.
static_rocket has joined #yocto
<barometz>
draw.io and plantuml are generally ok, for different use cases
fleg has joined #yocto
shoragan[m] has joined #yocto
<manuel1985>
barometz: I'll be using plantuml in the CI to render the uml descriptions, but figured I could need some help in drawing them in the first place.
<sef>
qschulz LetoThe2nd ty, i will check
esai[m] has joined #yocto
rfuentess has joined #yocto
jaskij[m] has joined #yocto
DavidM[m] has joined #yocto
GuilhemArvilMari has joined #yocto
falk0n[m] has joined #yocto
Saur[m] has joined #yocto
thomasd13 has quit [Ping timeout: 265 seconds]
<Guest6026>
For what it's worth. My issues with using classic sdk, cmake and find_package() were resolved by specifying --toolchain ~/sdk/sysroots/x86_64-xxsdk.linux/usr/share/cmake/OEToolchainConfig.cmake
<qschulz>
Guest6026: I believe/hope this should have been handled by the sourced script
<qschulz>
did you run cmake in the same terminal as the one you used to source the sdk script?
thierryE[m] has joined #yocto
hmw[m] has joined #yocto
<Guest6026>
yes, I did
paulg has joined #yocto
rob_w has quit [Remote host closed the connection]
eirikb[m] has joined #yocto
jarvis-owl[m] has joined #yocto
KurtKiefer[m] has joined #yocto
yocti has joined #yocto
jclsn[m] has joined #yocto
imuguruza89 has quit [Quit: Client closed]
xmn has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
Guest6026 has quit [Quit: Client closed]
seninha_ has joined #yocto
sef has quit [Ping timeout: 252 seconds]
sstiller has quit [Quit: Leaving]
florian_kc has quit [Ping timeout: 265 seconds]
sakoman has joined #yocto
seninha_ has quit [Quit: Leaving]
<vvn>
hi there -- is it a good idea to compile the kernel with all config as modules and install the necessary kernel-module-* in the target images, rather than fine tuning the kernel config?
zpfvo has quit [Ping timeout: 268 seconds]
Payam has quit [Remote host closed the connection]
<vvn>
The above config doesn't seem to compile all modules for linux-ti-staging...
tangofoxtrot has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
zpfvo has quit [Quit: Leaving.]
beneth has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
goliath has joined #yocto
florian has quit [Remote host closed the connection]
rfuentess has quit [Remote host closed the connection]
amitk has quit [Ping timeout: 268 seconds]
PhoenixMage has quit [Ping timeout: 265 seconds]
PhoenixMage has joined #yocto
PhoenixMage has quit [Ping timeout: 264 seconds]
PhoenixMage has joined #yocto
Tokamak has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
PhoenixMage has quit [Ping timeout: 244 seconds]
PhoenixMage has joined #yocto
florian_kc has joined #yocto
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
behanw has quit [Quit: Connection closed for inactivity]
sakoman has quit [Quit: Leaving.]
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
otavio has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
seninha has joined #yocto
mvlad has quit [Remote host closed the connection]
Payam has joined #yocto
ptsneves has quit [Ping timeout: 244 seconds]
florian_kc has quit [Ping timeout: 264 seconds]
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
goliath has joined #yocto
sakoman has joined #yocto
<fray>
ok, unrelated. Working on starting 2023 (porting everything in 2022.2 to master). I hit a problem with kmeta and openamp.. I don't understand the warning. (Not going to bug you with it today), when are you around next?
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
<fray>
crap wrong window
Tokamak has quit [Ping timeout: 244 seconds]
nemik has quit [Ping timeout: 244 seconds]
nemik has joined #yocto
Tokamak has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
Tokamak has quit [Read error: Connection reset by peer]
Tokamak has joined #yocto
seninha has quit [Remote host closed the connection]