-
Notifications
You must be signed in to change notification settings - Fork 794
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
Unable to build 1.0.1 with LTO #706
Comments
As netavark is now in the repositories, we have two providers of container-network-stack, so we add container-network-stack to provides. Disable LTO, as the plugins seem not compatible with it: containernetworking/plugins#706 Update the info around why we install to /opt/cni/bin as well. Remove unneeded explicit installation of /opt/cni/bin. Update maintainer info. git-svn-id: file:///srv/repos/svn-community/svn@1135253 9fca08f4-af9d-4005-b8df-a31f2cc04f65
As netavark is now in the repositories, we have two providers of container-network-stack, so we add container-network-stack to provides. Disable LTO, as the plugins seem not compatible with it: containernetworking/plugins#706 Update the info around why we install to /opt/cni/bin as well. Remove unneeded explicit installation of /opt/cni/bin. Update maintainer info. git-svn-id: file:///srv/repos/svn-community/svn@1135253 9fca08f4-af9d-4005-b8df-a31f2cc04f65
@dcbw this problem is still around with 1.2.0. Using a stale bot to hide this problem is not really great, as it means that this is likely never going to be fixed and actively discourages people to even report bugs 😢 |
Yeah, I suspect I need to tweak the stale bot's settings :-/. It's nice to have some old things cleaned out but it's too aggressive. (FYI I added a "keep" label for things that shouldn't go stale). |
@dvzrv none of us have enough go internals knowledge to fix this; do you know someone who could help out? |
It seems to me with 1.3.0 enabling LTO builds just fine, so perhaps this can be closed? In case you try it @dvzrv, perhaps you can also add $ /opt/cni/bin/bandwidth -v
CNI bandwidth plugin version unknown
CNI protocol versions supported: 0.3.0, 0.3.1, 0.4.0, 1.0.0 Similar issue to microsoft/azurelinux#6339. |
Hi! I am currently rebuilding cni-plugins as a package for Arch Linux. In the meantime we have switched to LTO by default (which can be switched off per package).
Unfortunately this fails with cni-plugins:
Full build log:
cni-plugins-1.0.1-build.log
We are currently building the plugins as follows:
Here CFLAGS, CPPFLAGS, CXXFLAGS and LDFLAGS are our distribution wide build flags.
Is this intentional or a bug?
The text was updated successfully, but these errors were encountered: