|
From: | Xin, Peixing |
Subject: | RE: config.sub patch: recognize four-part configuration name for VxWorks OS |
Date: | Fri, 8 Jan 2021 03:20:30 +0000 |
Hi John, Thanks much for your solution and info. I made some slight changes so that things can be correct and more clear. If this one can be merged, appreciated. Thanks, Peixing From: John Ericson <john.ericson@obsidian.systems> OK here is the my alternative that passes the same tests. In case any is interested, let me talk about underlying issue that makes this so non-intuitive (more than I initially expected!) is that there is a tension between gnu config thinking $kernel-$os and other tools thinking $os-$extra_info (Even though the $kernel $os env vars are new from me in ~ last 2 years, config.sub was informally parsing that way for decades.) This tension basically arose I think when someone reinterpreted linux-gnu not as GNU/linux, but Linux (an OS) + glibc ABI. The result is config.sub to cope is calling things like `eabihf` or `musl` valid OSs to be filtered later, which is awkward and unintuitive. Hopefully this can be untangled someday. (I would love to sit down with a bunch of interested parties and come up with e.g. a new JSON convention or something.) John On 1/7/21 10:13 AM, John Ericson wrote:
|
0001-Recognize-four-part-configuration-name-for-VxWorks.patch
Description: 0001-Recognize-four-part-configuration-name-for-VxWorks.patch
[Prev in Thread] | Current Thread | [Next in Thread] |