Re: config.sub patch: recognize four-part configuration name for VxWorks OS

2021-01-25 Thread Dmitry V. Levin
On Fri, Jan 08, 2021 at 03:20:30AM +, Xin, Peixing wrote: > 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 Applied, thanks! -- ldv

RE: config.sub patch: recognize four-part configuration name for VxWorks OS

2021-01-19 Thread Xin, Peixing
ged, appreciated. Thanks, Peixing From: John Ericson <mailto:john.ericson@obsidian.systems> Sent: Thursday, January 7, 2021 11:36 PM To: Xin, Peixing mailto:eixing@windriver.com>; mailto:config-patches@gnu.org Subject: Re: config.sub patch: recognize four-part configuration name for Vx

RE: config.sub patch: recognize four-part configuration name for VxWorks OS

2021-01-07 Thread Xin, Peixing
>>; config-patches@gnu.org<mailto:config-patches@gnu.org> Subject: Re: config.sub patch: recognize four-part configuration name for VxWorks OS 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-int

Re: config.sub patch: recognize four-part configuration name for VxWorks OS

2021-01-07 Thread John Ericson
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_i

Re: config.sub patch: recognize four-part configuration name for VxWorks OS

2021-01-07 Thread John Ericson
I don't this this patch is right. You are adding another "ad hoc" case, but we should strive not to do that. I will submit an alternative in a moment. On 1/7/21 12:16 AM, Xin, Peixing wrote: Hi , This patch is to recognize four-part configuration name for VxWorks. For example:     armv7m-