| 1 |
Consider this hypothetical KEYWORDS specifier I generated merging some |
| 2 |
gx86 and prefix content: |
| 3 |
|
| 4 |
KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc |
| 5 |
~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd |
| 6 |
~ppc-aix ~x64-freebsd ~x86-freebsd ~hppa-hpux ~ia64-hpux ~x86-interix |
| 7 |
~amd64-linux ~ia64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos |
| 8 |
~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris" |
| 9 |
|
| 10 |
I don't see a lot of stuff like the above ... well, anywhere. So ... |
| 11 |
is it wrong? I'm at a loss as to why it would be. |
| 12 |
|
| 13 |
Perhaps, is it SOP to rely on prefixes accepting gx86 keywords from |
| 14 |
non-prefix arch'es they correspond to? Doesn't that tend to defeat |
| 15 |
the whole purpose of having prefix-specific keywords as we move toward |
| 16 |
a single-shared-tree future? |
| 17 |
|
| 18 |
tia for any insights! |
| 19 |
|
| 20 |
-gmt |
Archives