<Guest7469>
the source command are build-openstlinuxweston-stm32mp1 and build-openstlinuxweston-MYMACHINE. What am I doing wrong?
Guest7469 is now known as DJ
DJ is now known as Guest7469
Guest7469 has quit [Quit: Konversation terminated!]
DeeJayInMelbourn has joined #yocto
camus1 has joined #yocto
camus has quit [Read error: Connection reset by peer]
camus1 is now known as camus
GNUmoon has quit [Ping timeout: 276 seconds]
kiran_ has quit [Ping timeout: 252 seconds]
GNUmoon has joined #yocto
xmn has quit [Ping timeout: 250 seconds]
camus has quit [Ping timeout: 240 seconds]
camus has joined #yocto
lowfi has quit [Quit: Leaving]
GNUmoon has quit [Ping timeout: 276 seconds]
mariusz has joined #yocto
DeeJayInMelbourn has quit [Quit: Konversation terminated!]
GNUmoon has joined #yocto
goliath has joined #yocto
Schlumpf has joined #yocto
codavi has quit [Ping timeout: 250 seconds]
rfuentess has joined #yocto
camus1 has joined #yocto
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
<JosefHolzmayrThe>
Guest7469: I don't completely understand what the problem you try to describe is?
mckoan|away is now known as mckoan
<mckoan>
good morning
<mckoan>
Guest4171: Interpretation of the ST documentation usually requires a run of runes. LOL
grma has joined #yocto
leon-anavi has joined #yocto
zpfvo has joined #yocto
kroon has joined #yocto
<wyre>
do you think could I use the linux-yocto kernel on my imx6? will this imply hardware problems?
<wyre>
I guess the point of using a vendor kernel is because of the specific hardware, isn't it?
<wyre>
also apparently the poky kernel is just compatible with qemu 🤔
<mckoan>
wyre: for imx6 you have to use the kernel provided by your vendor
<michalkotyla>
wyre: if it help you with something: I used mainline kernel without any special preparation (except device tree) so probably kernel from linux-yocto should work fine too
<michalkotyla>
wyre: on imx6 too of course
lucaceresoli has joined #yocto
<wyre>
thank you michalkotyla 😜
<JosefHolzmayrThe>
as ever so often, "it depends"
kroon has quit [Quit: Leaving]
<rburton>
Perceval[m]: add autoconf-archive to DEPENDS.
kroon has joined #yocto
<rburton>
tlwoerner: error says what the problem is. Don’t make the package group allarch?
sstiller has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
dev1990 has joined #yocto
<Perceval[m]>
autoconf-archive is already in the DEPENDS, that is why it is weird
dvorkindmitry has quit [Ping timeout: 250 seconds]
<coldspark29[m]>
Morning
<qschulz>
o/
zpfvo has quit [Ping timeout: 265 seconds]
zpfvo has joined #yocto
<coldspark29[m]>
Josef Holzmayr (TheYoctoJester): I am just watching the third episode of your tutorial. The package split doesn't work for me. ask is always there.
<JosefHolzmayrThe>
can you drop your state of the recipe into a pastebin? then i'll try to have a look later
kroon has quit [Remote host closed the connection]
kroon has joined #yocto
<coldspark29[m]>
I think there should rather be a notification when pulling honister. Like mind the changelog
<coldspark29[m]>
This is the Arch way btw
<coldspark29[m]>
Works now :)
lucaceresoli_ has joined #yocto
leonanavi has joined #yocto
<coldspark29[m]>
I find the syntax better though. It is more clear now
jsandman6 has joined #yocto
alicef_ has joined #yocto
alinucs_ has joined #yocto
mischief1 has joined #yocto
kroon has quit [Remote host closed the connection]
kroon has joined #yocto
rperier_ has joined #yocto
amitk has joined #yocto
davidinux1 has joined #yocto
Tokamak_ has joined #yocto
zeddiii has joined #yocto
lucaceresoli has quit [*.net *.split]
leon-anavi has quit [*.net *.split]
florian has quit [*.net *.split]
Tokamak has quit [*.net *.split]
amitk_ has quit [*.net *.split]
davidinux has quit [*.net *.split]
lexano has quit [*.net *.split]
pabigot has quit [*.net *.split]
dkl has quit [*.net *.split]
kernelspace has quit [*.net *.split]
Emantor has quit [*.net *.split]
mischief has quit [*.net *.split]
alicef has quit [*.net *.split]
Saur has quit [*.net *.split]
zeddii has quit [*.net *.split]
mario-goulart has quit [*.net *.split]
alinucs has quit [*.net *.split]
jsandman has quit [*.net *.split]
rperier has quit [*.net *.split]
beneth has quit [*.net *.split]
jsandman6 is now known as jsandman
davidinux1 is now known as davidinux
Emantor has joined #yocto
kernelspace has joined #yocto
mario-goulart has joined #yocto
lexano has joined #yocto
dkl has joined #yocto
florian has joined #yocto
Guest86 has joined #yocto
pabigot has joined #yocto
Saur has joined #yocto
beneth has joined #yocto
<rburton>
Perceval[m]: old release of yocto? maybe its needs a newer autoconf-archive. hard to say without more details, obviously works fine for everyone else.
<Perceval[m]>
rburton: yes I'm on warrior branch and using autoconf-archive_2018.03.13. I will try to upgrade autoconf-archive
<rburton>
warrior, ouch
<rburton>
yeah you'll most likely need to update autoconf-archive
<rburton>
you're aware warrior is EOL and unmaintained, right
<Perceval[m]>
yes I know :) I'm working on an update module, that's why I need to build warrior recipes
zpfvo has quit [Ping timeout: 250 seconds]
kroon has quit [Remote host closed the connection]
kroon has joined #yocto
zpfvo has joined #yocto
<rburton>
hm, great, buildhistory is broken
<coldspark29[m]>
@JPEW I just managed to set up Pyrex for our project and it is amazing. You can run parellel builds for multiple devices in parallel without having to set up multiple containers
<coldspark29[m]>
It really makes life a hell of a lot easier
<coldspark29[m]>
s/parellel//
camus1 has joined #yocto
<coldspark29[m]>
I am a Garmin fanboy now. If the Vivomove Style 2 comes out, I am definitely in :P
<rburton>
is anyone else seeing "/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__" from bitbake?
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
dvorkindmitry has joined #yocto
oberonc has joined #yocto
<oberonc>
ין
<oberonc>
hi
<oberonc>
I have a Telit LE910 modem I want to support
<oberonc>
for that I need (apparently) a kernel module ("qmi_wwan")
<oberonc>
.. which I dont have right now
<oberonc>
is there a recipe to add support for QMI modems ?
<oberonc>
I tried adding the module by myself by running "'bitbake -c menuconfig virtual/kernel"
<oberonc>
in the opened window I search for the kernel module where it should be
<RP>
rburton: some bad news. I think there is a separate lttng-tools arm bug to the one we were tracking :(
<rburton>
bah
<RP>
rburton: upstream found and fixed the relayd issue but we had an lttng-tools failure on the last -next run :(
<coldspark29[m]>
@JPEW An easy fix for the devtool edit-recipe to work, would be to just include vi or vim into the docker container. It will not be the host vim then, but at least you will get no error
<coldspark29[m]>
* docker container, I think. It
<barath>
hi all. I'm trying to follow the "Working with your own sources" part of the kernel dev guide and when I try to build my kernel bitbake complains that it could "Could not locate BSP definition" for the machine
<barath>
when grepping through the BSP guide for that term, nothing comes up. from googling, it actually seems to be related to the kernel "Recipe-Space Metadata", ie scc and cfg files related to the kernel + machine
<barath>
is that correct? is there a better definition for what "makes a BSP"? from skimming the BSP guide it seems like it's just another layer with hardware specific contents
<barath>
(I have my own custom machine conf btw and there's no pre-existing matching BSP, which is why I want to create my own BSP from scratch)
<qschulz>
coldspark29[m]: You're technically running multiple containers at the same time but yes, it's more or less hidden away from the user
<qschulz>
coldspark29[m]: what's the issue related to vim?
<qschulz>
ah, because edit-recipe starts an $EDITOR in the container I guess?
<coldspark29[m]>
@qschulz Yeah I like that
<coldspark29[m]>
Well, Josef uses devtool edit-recipe in his tutorials
<coldspark29[m]>
Pyrex complains that it doesnÄ
<qschulz>
yeah but he's not using containers AFAIR
<qschulz>
coldspark29[m]: doesn't what :) ?
<coldspark29[m]>
s/doesnÄ/doesn't find vi/
<coldspark29[m]>
Executing the host vim will be a challenge, although I read that you can somehow establish a named pipe
<coldspark29[m]>
I think it would be sufficient though to have vi or vim in the container. Then you just make a note somehwere that by using devtool edit-recipe will not use your host vim.
<coldspark29[m]>
By this, you will at least not get an error message
Guest86 has quit [Quit: Client closed]
<coldspark29[m]>
qschulz: I know but I think it would be good to have these commands in Pyrex to make it more accessible for beginners
<coldspark29[m]>
I am already trying to convince my colleagues that we should use it :P
gsalazar has joined #yocto
kroon has quit [Quit: Leaving]
<rburton>
vscode+pyrex integration would be neat, so it knows how to call out to the parent vscode for editing :)
<qschulz>
coldspark29[m]: the issue is that not everybody knows how to use vi/vim
<qschulz>
some might prefer emacs, some nano, etc..
<qschulz>
I assume we could install all main editors and pass the EDITOR environment variable to Pyrex container to use the same
<coldspark29[m]>
vi is the standard for devtool edit-recipe though
<qschulz>
coldspark29[m]: I'll read the code, but I'm surprised it's not using EDITOR
<coldspark29[m]>
qschulz: Yeah would be nice
camus1 has joined #yocto
<qschulz>
coldspark29[m]: it's using EDITOR, if not defined defaults to vi
camus has quit [Read error: Connection reset by peer]
<qschulz>
and this piece of code is in YP since morty, so I think we should do this :)
<qschulz>
coldspark29[m]: I'm sure JPEW will appreciate a Pull Request for that :)
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
<coldspark29[m]>
<qschulz> "coldspark29: I'm sure JPEW..." <- I can do it when I find the time. Have to still fix our signed bootloader booting the Yocto kernel this year
<qschulz>
coldspark29[m]: we probably want to make sure that if the user uses an unsupported EDITOR, we fallback to vi
<coldspark29[m]>
So you mean it should work if I put EDITOR=vim?
zpfvo has quit [Ping timeout: 240 seconds]
<coldspark29[m]>
I am pretty sure I have an alias vi="vim"
<qschulz>
coldspark29[m]: no, passing EDITOR to Pyrex
zpfvo has joined #yocto
<qschulz>
e.g. in envvars in pyrex.ini
<qschulz>
it'd still use the editor in the container, not the host
<coldspark29[m]>
Ah plus installing the editors in the containers I assume
<qschulz>
but at least, it'd be the same
<qschulz>
yes
<qschulz>
I assume vi/vim/nano/emacs should be enough?
<coldspark29[m]>
Sure
<qschulz>
I any case, we need vi, so a simple patch to add it to the images can be done ASAP and it'll probably fix your issue
<qschulz>
then we can make it a bit smarter/customizable :)
<coldspark29[m]>
It is not that urgetn
<coldspark29[m]>
I can manage without devtool. I think it would just be nice to have that fixed at some point
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
oberonc has quit [Quit: Client closed]
oberonc has joined #yocto
<oberonc>
about adding missing kernel modules
<oberonc>
here is what I did:
<oberonc>
bitbake -c menuconfig virtual/kernel
<oberonc>
bitbake -c diffconfig virtual/kernel
<oberonc>
got a fragment.cfg file (it included among others CONFIG_USB_NET_QMI_WWAN=m as I needed
<oberonc>
copied it to a files folder inside a recipe folder
<oberonc>
added a file called linux-kernel_%.bbappend
<oberonc>
it contains:
<oberonc>
SUMMARY = "Linux kernel customization"
<oberonc>
LINUX_VERSION = "5.10.63"
<oberonc>
inherit kernel
<oberonc>
SRC_URI += "file://fragment.cfg"
<oberonc>
I compiled the kernel using the command:
<oberonc>
bitbake virtual/kernel
<oberonc>
went ok
<oberonc>
now, when I create the image inself and look at its contents I dont see the modules
michalkotyla has quit [Ping timeout: 268 seconds]
gsalazar has quit [Ping timeout: 240 seconds]
<oberonc>
what am I mkissing/doing wrong ?
<oberonc>
missing
<rburton>
you didn't add it to the image
<rburton>
just because a package is produced doesn't mean it goes into every image
<rburton>
if you want every module in the image, add 'kernel-modules' to the image. that will pull in every module.
<rburton>
(each module is put into a separate package, so you need to install them)
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
<wyre>
is also ${systemd_unitdir} in FILES:${PN} by default?
<rburton>
use the systemd class and it will do the right thing
<qschulz>
wyre: bitbage-getvar FILES will probably answer your question
<qschulz>
bus as rburton said, inherit the systemd class :)
<wyre>
I'm already inheriting it ... but I'm not sure if I need to include my .service files in FILES:${PN} explicitly
<rburton>
well, look at the contents of the package
<rburton>
oe-pkgdata-util to the rescue
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 260 seconds]
zpfvo has joined #yocto
<tlwoerner>
rburton: thanks for the suggestion (i wasn't sure which part of the error message was most important)
kriive has joined #yocto
gsalazar has joined #yocto
oberonc has quit [Quit: Client closed]
<qschulz>
rburton: I understood Robert's mail the same way, I think they use catchall.bb as an image recipe without actually being an image recipe
<qschulz>
and then their image recipe is just adding catchall to the list of packages to install
<rburton>
but there's no way what he is describing can happen unless he is missing out a lot of steps
sakoman has joined #yocto
<qschulz>
rburton: do_install files from recipe-sysroot to ${D}
<rburton>
thats a terrible idea
<qschulz>
and FILES:${PN} = "/" I guess
<qschulz>
rburton: yup
<rburton>
if that is whats happening, it's fundamentally broken
prabhakarlad has quit [Quit: Client closed]
<RP>
rburton: it can't be as we filter the sysroots, you'd never get a working image out of them
<rburton>
right
<qschulz>
let's see what he's to say, I'm curious now :)
kroon has joined #yocto
<wyre>
why despite I've set DISTRO_FEATURE with systemd I cannot see systemd-analyze in the image?
<wyre>
rburton, so it's a separate package, right?
<rburton>
same recipe separate package
kroon has quit [Remote host closed the connection]
kroon has joined #yocto
xantoz has joined #yocto
jpuhlman_ has joined #yocto
jpuhlman is now known as Guest86
jpuhlman_ is now known as jpuhlman
Guest86 has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
manuel1985 has joined #yocto
davidinux has quit [Ping timeout: 240 seconds]
zpfvo has quit [Ping timeout: 250 seconds]
zpfvo has joined #yocto
camus has quit [Ping timeout: 250 seconds]
davidinux has joined #yocto
camus has joined #yocto
kiran_ has joined #yocto
zpfvo has quit [Ping timeout: 240 seconds]
zpfvo has joined #yocto
otavio has joined #yocto
Tokamak has joined #yocto
Tokamak_ has quit [Ping timeout: 268 seconds]
davidinux has quit [Ping timeout: 256 seconds]
davidinux has joined #yocto
<tlwoerner>
jonmason: i don't think anything in meta-rockchip is affected by the removal of -crypto from the cortexa72 tune
<tlwoerner>
jonmason: i don't know of any cortexa72-only SoCs, just the RK3399 which is cortexa72-cortexa53 (which is unaffected)
prabhakarlad has joined #yocto
vd has joined #yocto
GNUmoon has quit [Ping timeout: 276 seconds]
akiCA has joined #yocto
codavi has joined #yocto
gsalazar has quit [Ping timeout: 240 seconds]
akiCA has quit [Ping timeout: 252 seconds]
gsalazar has joined #yocto
GNUmoon has joined #yocto
<jonmason>
tlwoerner: it's about picking the better default, right?
<tlwoerner>
jonmason: i'm saying that only the cortexa72 tune was affected by the -crypto change, and we're not using the cortexa72 tune in meta-rockchip
<tlwoerner>
we're only using the cortexa72-cortexa53 tune (for rk3399)
<tlwoerner>
and it doesn't look like the cortexa72-cortexa53 tune is affected by this change
<tlwoerner>
?
<tlwoerner>
the cortexa72-cortexa53 tune always had a non-crypto and a -crypto option
<jonmason>
tlwoerner: ah, no worries then
camus has quit [Ping timeout: 240 seconds]
camus has joined #yocto
sstiller has quit [Remote host closed the connection]
GillesM has joined #yocto
mariusz has quit [Ping timeout: 265 seconds]
<manuel1985>
Is there a way for me to install all packages from a recipe?
<manuel1985>
Want all of the following: PACKAGES =+ "e2fsprogs-badblocks e2fsprogs-dumpe2fs e2fsprogs-e2fsck e2fsprogs-e2scrub e2fsprogs-mke2fs e2fsprogs-resize2fs e2fsprogs-tune2fs"
goliath has quit [Quit: SIGSEGV]
dtometzki has joined #yocto
<rburton>
manuel1985: no, because that's not all packages, that's a subset
<rburton>
e2fsprogs will pull in badblocks dump2fs mk2fs and e2fssck on its own
<rburton>
arguably it should recommend the others that it doesn't, so patches welcome
<manuel1985>
So I just need to install 'e2fsprogs' to get 'e2fsprogs-resize2fs'?