|
Bugzilla – Full Text Bug Listing |
| Summary: | GCC 11: cilium-proxy package fails | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Martin Liška <martin.liska> |
| Component: | Basesystem | Assignee: | Michał Rostecki <mrostecki> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P2 - High | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 1181859 | ||
|
Description
Martin Liška
2021-02-06 11:03:30 UTC
The same problem can be seen for this package: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/envoy-proxy/standard/x86_64 May I please ping this? May I please ping this as GCC 11 release is approaching? @Michael: May I please remind you this? This is an autogenerated message for OBS integration: This bug (1181866) was mentioned in https://build.opensuse.org/request/show/893862 Factory / boringssl (In reply to OBSbugzilla Bot from comment #5) > This is an autogenerated message for OBS integration: > This bug (1181866) was mentioned in > https://build.opensuse.org/request/show/893862 Factory / boringssl boringssl package update does not fix the compilation errors Workaround applied (using gcc10 package). That implies 'building against gcc11' is still unfixed - reopening @Michael: Any update on this please? I've sent a proposal of removing this package on the Kubic ML: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/QCQ2U4PPYD2K4X5CV6CCI45QUYQ5AK2O/ Making it green with gcc11 would require upgrading (or making some backports, which I would like to avoid). Due to some new "amazing" build features in Envoy and Bazel, I'm unable to build it offline on OBS and my old script/service (https://github.com/kubic-project/obs-service-bazel_repositories) doesn't work anymore. Let's see what the response on the ML is going to be, but I would rather spend my time on making Cilium working on rke2 with upstream container images rather than fighting with making Bazel OBS-friendly. Those images could be maybe slightly modified, maybe based on (open)SUSE, I'm fine with maintaining some set of Dockerfile patches as long as that doesn't require such craziness as I had to do with packaging Bazel projects. From my understanding, we are shifting into direction of rke2 being one of supported "k8s deployers" on MicroOS, so I think that offering Cilium through rke2 makes sense. The package was removed from Factory. |