On Mon, Aug 14, 2023 at 01:30:08AM -0700, Adam Joseph wrote:
> While reimplementing config.sub for use in a situation where no bash
> interpreter was available, I discovered several oddities about
> config.sub's behavior.
>
> One such oddity was the fact that an explicitly-provided vendor will
> b
While reimplementing config.sub for use in a situation where no bash
interpreter was available, I discovered several oddities about
config.sub's behavior.
One such oddity was the fact that an explicitly-provided vendor will
be clobbered by the inferred vendor for three cpu types: microblaze,
s390,
While reimplementing config.sub for use in a situation where no bash
interpreter was available, I discovered several oddities about
config.sub's behavior.
One such oddity was the fact that an explicitly-provided vendor will
be clobbered by the inferred vendor for three cpu types: microblaze,
s390,
