| Summary: | Add glibc-devel-static to prerequisites on OpenSUSE based host distributions | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Khem Raj <raj.khem> |
| Component: | autobuilder | Assignee: | Richard Purdie <richard.purdie> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | infras.ab.watcher, Infras.watcher, mhalstead, pidge, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Khem Raj
2019-09-18 02:26:36 UTC
For the record I strongly disagree with this. This in one failure, we don't have other reports of this and its from a patch in the dfu-utils recipe which enables static linking. I don't agree with arbitrarily adding host dependencies to resolve issues like this. If we want to have wider discussion, reach agreement and then add tests for the presence of libc.a, fine but right now I think this recipe should be fixed. We want to minimize host systems requirements where its practical to do so. (In reply to comment #1) > For the record I strongly disagree with this. This in one failure, we don't > have other reports of this and its from a patch in the dfu-utils recipe > which enables static linking. > dfu-utils is just showing the symptom of kind of inconsistency you have got there with prerequisites on different hosts. > I don't agree with arbitrarily adding host dependencies to resolve issues you can not call it arbitrary, there is a reason for it and why its failing as I have explained > like this. If we want to have wider discussion, reach agreement and then add > tests for the presence of libc.a, fine but right now I think this recipe > should be fixed. fixing the recipe is going to hide the underlying problem, yes it should be fixed for a different reason not the one you state. > > We want to minimize host systems requirements where its practical to do so. Thats a fair point. However, its probably helpful to call out that the prerequisites might install more or less components on different host distros, we only test a subset of metadata, therefore, these prerequisites are not a complete list that distribution might need. (In reply to comment #1) > For the record I strongly disagree with this. This in one failure, we don't > have other reports of this and its from a patch in the dfu-utils recipe > which enables static linking. > dfu-utils is just showing the symptom of kind of inconsistency you have got there with prerequisites on different hosts. > I don't agree with arbitrarily adding host dependencies to resolve issues you can not call it arbitrary, there is a reason for it and why its failing as I have explained > like this. If we want to have wider discussion, reach agreement and then add > tests for the presence of libc.a, fine but right now I think this recipe > should be fixed. fixing the recipe is going to hide the underlying problem, yes it should be fixed for a different reason not the one you state. > > We want to minimize host systems requirements where its practical to do so. Thats a fair point. However, its probably helpful to call out that the prerequisites might install more or less components on different host distros, we only test a subset of metadata, therefore, these prerequisites are not a complete list that distribution might need. I will close this as wontfix |