Re: [PATCH] * config.sub: Cordon off single-component aliases

[Ben Elliston]

Thanks, applied.

Ben


signature.asc
Description: PGP signature
___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches

Re: [PATCH] * config.sub: Cordon off single-component aliases

[Paul Eggert]

On 05/18/2018 05:42 PM, Ben Elliston wrote:

${parameter:-word} is in POSIX, but I don't know how portable it is to
old Bourne shells.  Paul?


Although it does not work on old Bourne shells, I suspect we don't need 
to worry about them any more.


The "Shellology" section of the Autoconf manual says ${VAR:-VALUE} 
causes old BSD shells to complain and die, and mentions Ultrix. However, 
as far as I know these old shells are now museum pieces. The last Ultrix 
release was in 1995. I haven't fielded an Ultrix bug report for many years.


For what it's worth, 'configure' scripts are still portable to Ultrix 
because they search for a POSIX-compatible shell by trying a list of 
programs that includes 'sh5', which was how Ultrix did it. I think this 
was due to the late Fred Canter, who specialized in getting the farkles 
out.  See:


Hall J. The last farkle. Linux J. 2007-12-02. 
https://www.linuxjournal.com/node/1005779



___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches

Re: [PATCH] * config.sub: Cordon off single-component aliases

[Ben Elliston]

On Thu, May 17, 2018 at 05:57:20PM -0400, John Ericson wrote:

> The 4th and last rule is the trickiest, and most fuzzy human. If the
> basic_machine was left as as, or appended with a vendor, I
> considered the pattern less an alias, and more a defaulting of a
> canonical or near canonical name. This seemed like a "higher
> quality" short-hand and thus one that is valid as part of a larger
> config. Instead of just hard-assigning `os`, however, I changed it
> to default `os` with
> 
>   os=${os:-DEFAULT}

${parameter:-word} is in POSIX, but I don't know how portable it is to
old Bourne shells.  Paul?

Cheers,
Ben

___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches

Re: [PATCH] * config.sub: Cordon off single-component aliases

[John Ericson]

To be really precise, with my change:

$ ./config.sub 386bsd-linux
Invalid configuration `386bsd-linux': machine `386bsd' not recognized

$ ./config.sub 386bsd
i386-pc-bsd

$ ./config.sub mingw32-bsd
Invalid configuration `mingw32-bsd': machine `mingw32' not recognized

$ ./config.sub mingw32
i686-pc-mingw32

John

On 05/18/18 13:11, John Ericson wrote:
"mingw32" would still work. Indeed I do not want to break 
compatability on intended short-hands like that. But "mingw32-vms" or 
something rediculous like that will no longer. (The "vms" is ignored 
currently.)


John

On May 18, 2018 10:00 AM, Earnie  wrote:



On 5/17/2018 5:57 PM, John Ericson wrote:
> Currently, there are number of aliases that expand both on their
own and as
> part of multi-component configurations. For example:
>
> $ ./config.sub 386bsd-linux
> i386-pc-bsd
>
> This change moves all of those to just trigger on a single field
branch,
> preventing their matching as part of larger components:
>
> $ ./config.sub 386bsd-linux
> Invalid configuration `386bsd-linux': machine `386bsd' not
recognized
>

This would not be kind.  I expect that config.sub gives the proper
triplet when doing ./config.sub mingw32.  Or am I not
understanding you?

The reason ./config.sub mingw32 returns the proper triplet is because
historically people, including many developers, have no idea what
i386-pc-mingw32 means when GCC and binutils creates a directory so
--host=mingw32 is given to create a mingw32 directory instead.

-- 
Earnie


___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches




___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches



___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches

Re: [PATCH] * config.sub: Cordon off single-component aliases

[John Ericson]

"mingw32" would still work. Indeed I do not want to break compatability on intended short-hands like that. But "mingw32-vms" or something rediculous like that will no longer. (The "vms" is ignored currently.)JohnOn May 18, 2018 10:00 AM, Earnie  wrote:



On 5/17/2018 5:57 PM, John Ericson wrote:

> Currently, there are number of aliases that expand both on their own and as

> part of multi-component configurations. For example:

> 

> 	$ ./config.sub 386bsd-linux

> 	i386-pc-bsd

> 

> This change moves all of those to just trigger on a single field branch,

> preventing their matching as part of larger components:

> 

> 	$ ./config.sub 386bsd-linux

> 	Invalid configuration `386bsd-linux': machine `386bsd' not recognized

> 



This would not be kind.  I expect that config.sub gives the proper

triplet when doing ./config.sub mingw32.  Or am I not understanding you?



The reason ./config.sub mingw32 returns the proper triplet is because

historically people, including many developers, have no idea what

i386-pc-mingw32 means when GCC and binutils creates a directory so

--host=mingw32 is given to create a mingw32 directory instead.



-- 

Earnie



___

config-patches mailing list

config-patches@gnu.org

https://lists.gnu.org/mailman/listinfo/config-patches


___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches

Re: [PATCH] * config.sub: Cordon off single-component aliases

[Earnie]

On 5/17/2018 5:57 PM, John Ericson wrote:
> Currently, there are number of aliases that expand both on their own and as
> part of multi-component configurations. For example:
> 
>   $ ./config.sub 386bsd-linux
>   i386-pc-bsd
> 
> This change moves all of those to just trigger on a single field branch,
> preventing their matching as part of larger components:
> 
>   $ ./config.sub 386bsd-linux
>   Invalid configuration `386bsd-linux': machine `386bsd' not recognized
> 

This would not be kind.  I expect that config.sub gives the proper
triplet when doing ./config.sub mingw32.  Or am I not understanding you?

The reason ./config.sub mingw32 returns the proper triplet is because
historically people, including many developers, have no idea what
i386-pc-mingw32 means when GCC and binutils creates a directory so
--host=mingw32 is given to create a mingw32 directory instead.

-- 
Earnie

___
config-patches mailing list
config-patches@gnu.org
https://lists.gnu.org/mailman/listinfo/config-patches