-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Build breaks on Zephyr RTOS v3.4.0 #229
Comments
Thanks for reporting it.
@entire Do you know if there is any Zephyr environment variable that can be used at compile time to identify the version? |
@cguimaraes It looks like the low-level "interface" is to |
Thank you @bryceschober for the input. It was very helpful to improve the Zephyr version detection within Zenoh-Pico. There is a partial fix for this issue, until the new Zephyr multicast API is integrated: #230 @entire if this is a blocking point for you but you do not need Zenoh multicast transport, you might want to set |
seems to work, thanks! @cguimaraes |
Describe the bug
Seems like there was a change that breaks
zenoh-pico/src/system/zephyr/network.c
in the network interface APIs, since Zephyr v3.4.0 (https://docs.zephyrproject.org/latest/releases/release-notes-3.4.html) it now takes additional,struct net_if * iface
parameter::c:func:
net_if_ipv4_maddr_join
:c:func:
net_if_ipv4_maddr_leave
:c:func:
net_if_ipv6_maddr_join
:c:func:
net_if_ipv6_maddr_leave
It works with Zephyr RTOS v3.3.0 before the change was made.
To reproduce
west init && west build
locally, followed https://github.com/cguimaraes/zenoh-pico-zephyr-example exampleSystem info
The text was updated successfully, but these errors were encountered: