frosteyes has quit [Remote host closed the connection]
frosteyes has joined #yocto
michaelo has quit [Ping timeout: 252 seconds]
michaelo has joined #yocto
KhazAkar has joined #yocto
rfuentess has joined #yocto
shoragan_ is now known as shoragan
mckoan|away is now known as mckoan
goliath has joined #yocto
zpfvo has joined #yocto
rusam has joined #yocto
Kubu_work has joined #yocto
alperak has joined #yocto
rusam has quit [Quit: Leaving...]
<LetoThe2nd>
yo dudX
<mckoan>
LetoThe2nd: hi
leon-anavi has joined #yocto
<LetoThe2nd>
yo mckoan
alperak has quit [Ping timeout: 250 seconds]
mvlad has joined #yocto
vladest has quit [Quit: vladest]
Guest9764 has joined #yocto
Guest9764 is now known as Rich_1234
frieder has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
dvergatal has quit [Ping timeout: 256 seconds]
dvergatal has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
vladest has joined #yocto
radanter has joined #yocto
frieder has quit [Ping timeout: 245 seconds]
egueli-AV has joined #yocto
florian_kc has joined #yocto
frieder has joined #yocto
mbulut has joined #yocto
alperak has joined #yocto
frieder has quit [Ping timeout: 245 seconds]
olani has quit [Remote host closed the connection]
ptsneves has joined #yocto
olani has joined #yocto
vladest has quit [Remote host closed the connection]
vladest has joined #yocto
ptsneves has quit [Ping timeout: 255 seconds]
ptsneves has joined #yocto
frieder has joined #yocto
ptsneves has quit [Ping timeout: 268 seconds]
neofutur has quit [Ping timeout: 252 seconds]
neofutur has joined #yocto
egueli-AV has quit [Read error: Connection reset by peer]
egueli-AV has joined #yocto
Omax has quit [Ping timeout: 255 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
prabhakarlad has joined #yocto
prabhakar has joined #yocto
kulos75 has joined #yocto
ptsneves has joined #yocto
030AAB7NT has joined #yocto
starblue has quit [Ping timeout: 256 seconds]
starblue has joined #yocto
<030AAB7NT>
Hi, I have a problem, I don't know if this channel is the best to discuss about it or not. In our Yocto device, the network (DHCP and everything) is managed by systemd. This is maybe the default behavour. But we have a problem with systemd, the problem is discribed here: https://github.com/openthread/ot-br-posix/issues/974 we have otbr-agent on the board that send RA packets, the problem is, systemd
<030AAB7NT>
should ignore RA packets from local but it doesn't, so it try to set this on the kernel but when the kernel receive it, there is an error and when this error happens, systemd have some "parts" that stop working: For exemple the DHCP client stop working... I temporary I fix the issue by setting IPv6AcceptRA=no in systemd configuration. But the problem is: I need to receive RA from outside and process
<030AAB7NT>
them. And I don't understand, when I set "/proc/sys/net/ipv6/conf/eth0/accept_ra" to "2", when the board receive a RA (I see it with tcpdump or radvdump), the route is not added. So is there a solution for the RA to work "outside of systemd" when the network is managed by systemd ?
030AAB7NT is now known as tyaku_
<alperak>
I don't have knowledge but there is a channel called "#systemd". Maybe you can get help from there.
<alperak>
tyaku_
JaMa has quit [Ping timeout: 260 seconds]
<tyaku_>
Thanks, I'm going to ask there
<RP>
Why does expanding SOURCE_DATE_EPOCH cause the CDN sstate test to hang? :(
JaMa has joined #yocto
Omax has joined #yocto
hcg has joined #yocto
otavio has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
lexano has joined #yocto
tnovotny has joined #yocto
<tyaku_>
Currently we identify two methods to "solve/bypass" the systemd bug:
<tyaku_>
1. Put an iptables rules to make sure that systemd *don't see* the packets emited localy (But I really don't think it's possible)
<tyaku_>
2. Update systemd to a newer version... But if I do it, maybe all the recipes everywhere will not be compatible in terms of syntax [...]
<tyaku_>
I am on Hardknott, systemd is v247, I need to go at v250 minimum.
adrian_s has quit [Ping timeout: 260 seconds]
adrian_s has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
thomas_34 has joined #yocto
<thomas_34>
Hello guys, I have some trouble with a package that should provide a native tool. In the recipe of that packge (swig) there is this line: BBCLASSEXTEND = "native nativesdk"
<thomas_34>
For my understanding, bitbake should built now this package also for the host right? Not only for the target.
<thomas_34>
But when I checked the logs of that package (do_compile and do_install), it used the target compiler, to build the package and also installed it to ".../work/aarch64-linux/" which is the architecture of my target.
<thomas_34>
How I can track down further the issue?
<tyaku_>
What is the easiest way to update the systemd version ? I try to set SRC_REV in a bbappend, but I get issues when patches are applied.
<tyaku_>
New idea: take a systemd.bb from a recent yocto version to define multiple systemd versions and used a prefered
<yocton>
thomas_34: have you tried to build <your_tool>-native (this is the name bitbake will give to the native version of your recipe)
<tyaku_>
But I don't know if it's good, has systemd has a systemd.inc file with SRC_REV, and this file seems to be imported by multiple files.
CrazyGecko has joined #yocto
<yocton>
thomas_34: if your tool is native only, you should name the recipe <your_tool>-native.bb and "inherit native" from it. This way, bitbake does not tried to compile your tool for the target
<thomas_34>
yocton, oh god - what a rookie mistake. No I didnt. Thank you very much, Ill do that now and double check
<alperak>
tyaku_ I understand that you are trying to backport.
<alperak>
You can directly take the whole systemd directory and put it in your own meta-layer. In order to use the systemd you want, you need to set PREFERRED_VERSION or increase the priortiy of the meta-layer.
<egueli-AV>
I noticed that Bitbake builds bluez5 and other recipes I don`t need. But they don`t appear in the final image. That`s relieving but I wonder what decides what goes in the image and what doesn`t?
vvmeson is now known as vmeson
<tyaku_>
I have an issue with meta-imx, because it create a patch on systemd using a bbappend with % so no version. Of course it is not compatible with my new systemd version
<tyaku_>
I fixed it temporary by changing systemd_%.bbappend by systemd_247.6.%.bbappend but what is the correct way in this case ?
arisut has quit [Quit: install gentoo]
<alperak>
tyaku_ I think I'd do the same. If someone with knowledge explains it, we can learn the proper way.
arisut has joined #yocto
<tyaku_>
Yeah but this solution is very bad because meta-imx is not mine!
<tyaku_>
(so i'm not supposed to change anything in this)
sakman has quit [Ping timeout: 268 seconds]
<Saur>
tyaku_: Typically you would put a bbappend in one of your own layers to revert whatever meta-imx is doing.
vladest has quit [Remote host closed the connection]
<rburton>
egueli-AV: most likely packagegroup dependencies meaning stuff needs to be built. you can remove bluetooth from your DISTRO_FEATURES and it won't build any bluez, etc.
<rburton>
egueli-AV: check the existing value of DISTRO_FEATURES and remove anything you don't need
sakman has joined #yocto
<alperak>
egueli-AV In addition, depending on the version you are using, you can use "bitbake-getvar DISTRO_FEATURES" or "bitbake -e | grep ^DISTRO_FEATURES=" for debugging.
arisut has quit [Quit: install gentoo]
arisut has joined #yocto
alessioigor has quit [Quit: alessioigor]
GNUmoon has quit [Ping timeout: 240 seconds]
alessioigor has joined #yocto
Haxxa has quit [Ping timeout: 264 seconds]
<tyaku_>
After replacing systemd 247 by systemd 250 I have this error during the do_rootfs.. The postinstall intercept hook 'update_udev_hwdb' failed
Haxxa has joined #yocto
<tyaku_>
IDK what is 'update_udev_hwdb' for, I see that it is on the recipe but IDK what it does
tnovotny has quit [Remote host closed the connection]
rfs613- is now known as rfs613
Haxxa has quit [Ping timeout: 256 seconds]
GNUmoon has quit [Ping timeout: 240 seconds]
GNUmoon has joined #yocto
<thomas_34>
A short question: If I have a package A which DEPENDS on swig-native
kulos75 has quit [Quit: Konversation terminated!]
<thomas_34>
A short question: If I have a package "A" which DEPENDS on "swig-native": Where is swig-native provided when I build "A"? Should it be somewhere in the work directory of "A"? Can someone explain that please?
<thomas_34>
Is there maybe some bitbake variable, which I can use within the "A"-recipe as a reference to get "access" to the swig-native binary?
Net147 has quit [Ping timeout: 256 seconds]
Haxxa has joined #yocto
goliath has quit [Quit: SIGSEGV]
<olani>
thomas_34: It should be in tmp/work/*/A/VER/recipe-sysroot-native
<olani>
thomas_34: And that should be on the PATH for any tasks in recipe A.
<thomas_34>
Thanks olani. So if it does not show up in */recipe-sysroot-native then there is something wrong with the DEPENDS in A?
GNUmoon has quit [Ping timeout: 240 seconds]
Haxxa has quit [Ping timeout: 255 seconds]
CrazyGecko has quit [Quit: Leaving]
GNUmoon has joined #yocto
Haxxa has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
Net147 has joined #yocto
thomas_34 has quit [Quit: Client closed]
<rburton>
yes
frieder has quit [Remote host closed the connection]
bhstalel has joined #yocto
pidge has joined #yocto
jmd has joined #yocto
tyaku_ has quit [Quit: Lost terminal]
florian_kc has quit [Ping timeout: 255 seconds]
sakman_ has joined #yocto
Vonter has quit [Ping timeout: 260 seconds]
LDericher has quit [Ping timeout: 256 seconds]
JaMa has quit [Read error: Connection reset by peer]
Chaser has quit [Remote host closed the connection]
Chaser has joined #yocto
bhstalel has quit [Quit: Client closed]
rfuentess has quit [Remote host closed the connection]
JerryM has quit [Quit: Konversation terminated!]
zpfvo has quit [Remote host closed the connection]
mbulut has quit [Ping timeout: 255 seconds]
mvlad has quit [Ping timeout: 260 seconds]
mckoan is now known as mckoan|away
alperak has quit [Quit: Client closed]
alessioigor has quit [Read error: Connection reset by peer]
alessioigor has joined #yocto
alperak has joined #yocto
radanter has quit [Remote host closed the connection]
mvlad has joined #yocto
alperak has quit [Client Quit]
nerdboy has quit [Ping timeout: 255 seconds]
nerdboy has joined #yocto
nerdboy has joined #yocto
nerdboy has quit [Changing host]
<halstead>
kanavin_: It appears you managed to ssh into ubuntu1804-arm-1 and kick off some processes mid-maintenance. Can you exit gracefully so I can complete the process?
nerdboy has quit [Remote host closed the connection]
adrian_s has quit [Ping timeout: 260 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
<rfs613>
I recall reading some rules about use of ${S} and similar variables in different stages of do_compile, do_install, etc.
<rfs613>
but I can't find them anymore, does anyone have a pointer?
adrian_s has joined #yocto
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
alessioigor has quit [Quit: alessioigor]
Chaser has quit [Quit: Chaser]
nerdboy has quit [Remote host closed the connection]
nerdboy has joined #yocto
<halstead>
kanavin_: I went ahead and killed those processes.
leon-anavi has quit [Remote host closed the connection]