| Summary: | dev-util/catalyst-9999: silent fail when custom subarch defined | ||
|---|---|---|---|
| Product: | Gentoo Hosted Projects | Reporter: | Azamat H. Hackimov <azamat.hackimov> |
| Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | damiandudycz |
| Priority: | Normal | Keywords: | PATCH |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | 0001-Introduce-basearch-settings.patch | ||
Thanks. Could you send this to the gentoo-catalyst mailing list? (In reply to Sam James from comment #1) > Thanks. Could you send this to the gentoo-catalyst mailing list? -> https://marc.info/?l=gentoo-catalyst&m=169087837018281&w=2, still needs to be applied I can confirm this issue, I have that problem with cell subarch from ppc64 family. |
Created attachment 866757 [details, diff] 0001-Introduce-basearch-settings.patch When custom subarch is defined ("core2", for example), it will override hostarch, and all logic for creation bootloader entries and ISO image will be broken. Introduced basearch variable that may used for these cases. Added some die statement in some case switches for default values to prevent silent failure.