| Summary: | Add strip-unsupported-flags function to flag-o-matic eutils | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Douglas Russell (RETIRED) <puggy> |
| Component: | Unclassified | Assignee: | Douglas Russell (RETIRED) <puggy> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Patch for flag-o-matic eclass adding strip-unsupported-flags
Updated to reflect other changes in flag-o-matic |
||
|
Description
Douglas Russell (RETIRED)
2003-08-11 03:05:54 UTC
Created attachment 15893 [details, diff]
Patch for flag-o-matic eclass adding strip-unsupported-flags
we already have `gcc2-flags` ... why not make a `gcc3-flags` and a wrapper function named `strip-incompat-flags` or whatever, like you have Well. I could do that, but I thought this was a good method as it does not rely on having a list of compatible flags and will work with all versions of gcc present and probably future without updating... Sorry if I've misunderstood your thinking here. Puggy nah, i assumed your function worked in a manner similar to the other function i like your implementation ;) Created attachment 20036 [details, diff]
Updated to reflect other changes in flag-o-matic
Added to flag-o-matic eutils. Puggy |