-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
isisd: staticd: need to link directly against libyang #14664
Conversation
Signed-off-by: Christian Hopps <[email protected]>
@Mergifyio backport dev/9.1 stable/9.0 |
✅ Backports have been created
|
I know this is merged, just trying to clarify – why only isisd and staticd? What's different about these daemons? I don't see such linking in ripd, bfdd, etc. |
Almost all uses of libyang happen in libfrr which is already linked against libyang. These daemons used a couple static inline "getter" functions (e.g., |
isisd: staticd: need to link directly against libyang (backport #14664)
Thanks. Maybe it would be better to have wrappers for such functions in libfrr instead of additional linking, but it's not a big deal. |
isisd: staticd: need to link directly against libyang (backport #14664)
@Mergifyio backport stable/8.5 |
✅ Backports have been created
|
@Mergifyio backport stable/8.4 |
✅ Backports have been created
|
@Mergifyio backport stable/8.3 |
✅ Backports have been created
|
@Mergifyio backport stable/8.2 |
✅ Backports have been created
|
isisd: staticd: need to link directly against libyang (backport #14664)
isisd: staticd: need to link directly against libyang (backport #14664)
isisd: staticd: need to link directly against libyang (backport #14664)
isisd: staticd: need to link directly against libyang (backport #14664)
No description provided.