Re: [PATCH] config.guess: Guess vendor for *-android-linux-*

On Sat, Apr 5, 2025, at 7:38 AM, sin-ack via Patches for the config.guess and config.sub scripts wrote: ... > Setting the vendor to "android" lets us tell the software that even > though the GNU ABI is in effect, certain restrictions are present due > to running on Android. Please don't use the v

Re: [Patch] config.guess, config.sub: Include support for sw_64 arch

On Sun, Jan 12, 2025, at 11:06 AM, Funda Wang wrote: > As you may know, there has been a new architecture named "sw_64", which > is used by ShenWei[1] chips inspired by DEC Alpha. > > I've proposed a patch[2] against config.guess and config.sub, which will allow > sw_64 be recognized so that softw

Re: 回复：Re: llvm configure failed ，please help me------uable to guess system type

lease also continue to cc: the mailing list so the discussion is recorded for future people with the same question. On Mon, Dec 16, 2024, at 10:57 PM, 龙雨洁 wrote: > Zack Weinberg 在 2024年12月17日 周二 2:25 写道： > > On Mon, Dec 16, 2024, at 2:18 AM, 龙雨洁 wrote: > > > This script (versio

Re: llvm configure failed ，please help me------uable to guess system type

Please be advised that config-patches is a traditional mailing list where we stick to the old convention of "bottom posting", that is, replying to each piece of your message *underneath* that piece. Keep reading for my actual reply. Please use this convention yourself when replying. On Mon, Dec 1

Re: Possible typo in config.sub

On Sat, Jul 6, 2024, at 12:36 AM, Shiro Kawai wrote: > Hi there, my first post to this list. > I was browsing config.sub and stumbled on a possible typo. You are correct. I posted the same patch more than a month ago but it has not been applied. FYI, patches to config.sub and config.guess go to

Re: [gnu.org #2067223] Need help setting up redirects in /software/config

On Wed, Jun 12, 2024, at 3:16 PM, Therese Godefroy via RT wrote: > Le Mer 12 Juin 2024 10:23:52, z...@owlfolio.org a écrit : >> Me and the maintainers of `config.sub` and `config.guess` (cc:ed) are >> trying to set up some HTTP redirects so that when config.guess fails >> it can print out a long-te

Need help setting up redirects in /software/config

Me and the maintainers of `config.sub` and `config.guess` (cc:ed) are trying to set up some HTTP redirects so that when config.guess fails it can print out a long-term stable URL for a newer version of itself, instead of a URL that involves specifics of the VCS-to-web bridge for the project, which

Re: [PATCH v2 1/4] config.guess: Avoid implicit int in definitions of main.

On Mon, May 13, 2024, at 4:55 PM, Zack Weinberg wrote: > From: Petr Vorel > > Implicit ‘int’ (e.g. ‘extern foo();’ meaning the same thing as > ‘extern int foo();’) was dropped from the C standard in its 1999 > edition. Twenty-five years later, free C compilers are finally > sta

Re: [RFC PATCH 00/15] config.sub bug fixes

On Mon, Jun 3, 2024, at 3:28 PM, Zack Weinberg wrote: > I applied a coverage analyzer to config.sub trying to find all the > code paths that currently aren't being tested. (Did you know there > are coverage analyzers for shell scripts? I was halfway expecting > it to be im

[RFC PATCH 13/15] config.sub: improve consistency of shorthands and X-Y partial names.

It seems to me that if ‘fooco’ expands to ‘cpu-fooco-foonlyos’, where ‘cpu’ is whatever CPU was hip at the time Fooco was making computers, then ‘cpu-fooco’ should also expand to ‘cpu-fooco-foonlyos’, and ‘cpu-foonlyos’ should as well, except when ‘foonlyos’ is something generic like ‘sysv’ or ‘bsd

[RFC PATCH 01/15] config.sub: testsuite: whitespace and sorting corrections.

Ensure that the second column of testsuite/config-sub.data is consistently indented—always to the same distance, using tabs— and that the entire file is properly sorted. No functional change. It might make sense to swap the two columns of this file and then re-sort it, which would group all the a

[RFC PATCH 07/15] config.sub: handle cNN-convex and convex-cNN shorthands correctly.

convex-cNN and cNN-convex (where NN in 1, 2, 32, 34, 38) are supposed to be shorthands for cNN-convex-bsd, but the code to handle them was in the wrong switch statement, making it unreachable. Fix. https://en.wikipedia.org/wiki/Convex_Computer says there was also a C4 machine in this product line

[RFC PATCH 08/15] config.sub: don’t override OS for c90-cray.

Fix a typo in the logic for handling the OS default for c90-cray, causing c90-cray-[anything] to get overridden to c90-cray-unicos. I’m not aware of any non-Unicos operating systems for the C90, but let’s not be a pointless obstacle for anyone who wants to write one. (For testing purposes I used Li

[RFC PATCH 10/15] config.sub: normalize nextstep/openstep consistently.

Normalize the names for NeXT’s operating systems consistently. The version number bump from 2 to 3 went along with a marketing name change from “nextstep” to “openstep”, which was being honored, or not, depending on what shorthand you put in and what CPU you selected (!) Consistent with the treatm

[RFC PATCH 11/15] config.sub: remove two unreachable case clauses.

These attempt to perform normalizations that were already done by code above this point, so they are unnecessary. There are already test cases for these normalizations. --- config.sub | 6 -- 1 file changed, 6 deletions(-) diff --git a/config.sub b/config.sub index 3f667ea..9305b40 100755 --

[RFC PATCH 00/15] config.sub bug fixes

from people who remember these old systems (most of them appear to have been from the 1980s and early 1990s, before my time). zw Zack Weinberg (15): config.sub: testsuite: whitespace and sorting corrections. config.sub: disable shellcheck warning SC2162 globally. config.sub: flatten and

[RFC PATCH 14/15] config.sub: add missing CPUs, vendors, and OSes.

Add the following entries to the tables of valid CPUs, vendors, and operating systems: CPUs: v810 Vendors: acorn, atari, be, ccur, commodore, digital, intergraph, rebel, rom68k, rombug, semi, siemens, sni, stratus, tektronix OSes: atheos, chorusos, psos, syllable, wince Evide

[RFC PATCH 03/15] config.sub: flatten and sort long case-alternative lists

Several of these lists are going to be modified substantially in the next few patches, this will make it much easier to see what is going on. No functional change. --- config.sub | 535 +++-- 1 file changed, 434 insertions(+), 101 deletions(-) diff

[RFC PATCH 15/15] config.sub: testsuite: add 121 more test cases.

These all hit code paths that were not already being tested, but produce (what appears to be) the correct canonical name without requiring any more code changes. --- testsuite/config-sub.data | 121 ++ 1 file changed, 121 insertions(+) diff --git a/testsuite/co

[RFC PATCH 09/15] config.sub: don’t override OS for blackfin, m68knommu, parisc.

A similar issue to the previous patch: make the OS default for the CPU aliases “blackfin,” “m68knommu,” and “parisc” actually be a default and not an override. There have been many OSes for PA/RISC. Both blackfin and m68knommu are definitely used in bare-metal configuration as well as with an OS.

[RFC PATCH 12/15] config.sub: Treat i386-pc-rtmk-nova as a 4-part system name.

Handle ‘i386-nova’ as shorthand for a 4-part system name, kernel=rtmk os=nova, instead of a canonicalized OS name with a dash in the middle, os=rtmk-nova. RTMK is a microkernel. Nova is an OS written on top of that microkernel. The sho

[RFC PATCH 05/15] config.sub: consistently use sun as default vendor for solaris*.

config.sub had a rule that os=sunos* implies vendor=sun unless the vendor has already been set for some other reason, but no such rule for os=solaris*, and that meant `./config.sub sparc-solaris2` was inconsistent with what you’d get from config.guess on that system. Add the missing rule. Unlike

[RFC PATCH 06/15] config.sub: accept knetbsd-gnu, netbsd-gnu, uclinux-gnu.

There is evidence elsewhere in config.sub, and in config.guess, indicating that knetbsd-gnu, netbsd-gnu, and uclinux-gnu were supposed to be acceptable combinations of $kernel and $os, but they are currently being rejected. Add them to the list of acceptable kernel-os combinations, and add test ca

[RFC PATCH 04/15] config.sub: correct Bull DPX/2-[123]00 and DPX/20 canonical names.

config.sub was mapping all single-component shorthands matching the shell glob `dpx2*` to ‘m68k-bull-sysv3’, which is incorrect. Of the four different machines once manufactured by Groupe Bull whose model number can be abbreviated ‘dpx2something’, only two were m68k-based: the DPX/2-200 and DPX/2-

[RFC PATCH 02/15] config.sub: disable shellcheck warning SC2162 globally.

With the version of shellcheck I have (0.9.0), the existing attempts to disable SC2162, above each use of read without -r, do not work because they are not on the line *immediately* previous to the read command — there’s always a “saved_IFS=$IFS” line in between. Since this script must not use rea

Re: Archaeology time: Help me identify these ancient OSes and vendors

[off-list reply was because of technical limitations so returning to the list] On Tue, May 28, 2024, at 8:28 AM, Mikael Pettersson wrote: > You wrote: >> These are probably all either vendor or OS names from the late 1980s or >> early 1990s. Can anyone help me fill out the following list of thing

Archaeology time: Help me identify these ancient OSes and vendors

I've been trying to fill in as many gaps as possible in the config.sub test suite (and finding a whole bunch of actual bugs in the process). I have a short list of inputs where the actual code to handle them is incomplete or broken, there's nothing in config.guess to use as a clue, and I don't know

Re: [PATCH v2 0/4] config.patches improvements

On Mon, May 13, 2024, at 8:55 PM, Zack Weinberg wrote: > Round 2 of my and Petr Vorel's patch set to polish up config.guess > a little. The first two patches are the most important, as they > future-proof config.guess against new C compilers that object to > implicit int and/or o

Re: [PATCH v2 4/4] config.guess: Improve behavior when uname output is not understood.

On Mon, May 13, 2024, at 8:55 PM, Zack Weinberg wrote: > If we get to the bottom of the big switch in config.guess without > having a guess, we try two things, in this order: > > - Compiling and running a C program that knows about a bunch of really > old systems that did n

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

On Tue, May 14, 2024, at 12:31 PM, Dmitry V. Levin wrote: >> > On Tue, May 14, 2024 at 10:34:11AM -0400, Zack Weinberg wrote: >> >> --- /dev/null 2024-05-14 09:16:42.181936154 -0400 >> >> +++ .htaccess 2024-05-14 09:32:57.063158152 -0400 >> >&

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

On Tue, May 14, 2024, at 9:51 AM, Alyssa Ross wrote: >> Turns out /software/config is under our control, in the same way that >> /software/autoconf is. It should be sufficient to apply this patch to the >> config-web CVS repository (https://savannah.gnu.org/cvs/?group=config): >> >> --- /dev/null

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

On Mon, May 13, 2024, at 11:33 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >> On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote: >>> Zack Weinberg wrote: >>>> (N.B. The Savannah URLs look a little too cgit-specific to trust >>>> that they will

[PATCH v2 2/4] config.guess: Modernize C programs a bit more.

Specifically, eliminate all uses of implicit function declarations and of old-style function definitions for functions that take arguments. Many of the C programs embedded in config.guess are only used on very old systems that may never have had an ISO C compiler (other than GCC, which we cannot a

[PATCH v2 1/4] config.guess: Avoid implicit int in definitions of main.

; but we can worry about that if and when it comes up. Signed-off-by: Petr Vorel Co-authored-by: Zack Weinberg --- config.guess | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/config.guess b/config.guess index f6d217a..b7f5e24 100755 --- a/config.guess +++ b

[PATCH v2 4/4] config.guess: Improve behavior when uname output is not understood.

If we get to the bottom of the big switch in config.guess without having a guess, we try two things, in this order: - Compiling and running a C program that knows about a bunch of really old systems that did not have a uname command. - A specific test for Apollo systems, which doesn’t require a

[PATCH v2 3/4] config.guess: Revise diagnostic output produced on failure.

The output now varies based on which of three different situations is detected: 1. If config.guess’s embedded timestamp is more than three years old, we instruct the user to update it from Savannah, and we don’t say anything else. 2. If we tried to use a C compiler but none was found (not j

[PATCH v2 0/4] config.patches improvements

ss: Avoid implicit int in definitions of main. Zack Weinberg (3): config.guess: Modernize C programs a bit more. config.guess: Revise diagnostic output produced on failure. config.guess: Improve behavior when uname output is not understood. config.guess | 251 +

Re: [PATCH] Revise the diagnostic output produced when config.guess fails.

On Thu, Apr 4, 2024, at 6:50 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >>The duplicate uname -m/-r/-s/-v output is replaced with >>diagnostics of the availability of uname and a C compiler. > > I would suggest keeping the duplicate uname output; config.guess

Re: [PATCH] Modernize more C programs in config.guess.

On Thu, Apr 4, 2024, at 6:25 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >> -$CC_FOR_BUILD -o "$dummy" "$dummy.c" && >> - dummyarg=`echo "$UNAME_RELEASE" | sed -n 's/\([0-9]*\).*/\1/p'` && >> -

[PATCH] Modernize more C programs in config.guess.

From: Zack Weinberg Specifically, on top of Petr Vorel’s patch, eliminate all use of old-style function definitions and implicit function declarations. Many of the C programs embedded in config.guess are only used on very old systems that may never have had an ISO C compiler (other than gcc

[PATCH] Revise the diagnostic output produced when config.guess fails.

From: Zack Weinberg The output now varies based on which of three different situations is detected: 1. If config.guess’s embedded timestamp is more than three years old, we instruct the user to update it from Savannah, and we don’t say anything else. 2. If we tried to use a C compiler

Re: [PATCH 1/1] config.guess: Use int

On Wed, Apr 3, 2024, at 1:49 PM, Petr Vorel wrote: >> On Wed, Apr 3, 2024, at 1:01 PM, Petr Vorel wrote: >> > Although -Wmain-return-type is not considered as error (unlike >> > -Wimplicit-int on gcc 14 and clang 16), but just a warning, let's fix it >> > for the future. >> We want the end result t

Re: [PATCH 1/1] config.guess: Use int

On Wed, Apr 3, 2024, at 1:01 PM, Petr Vorel wrote: > Although -Wmain-return-type is not considered as error (unlike > -Wimplicit-int on gcc 14 and clang 16), but just a warning, let's fix it > for the future. > > :1:1: warning: return type of 'main' is not 'int' [-Wmain-return-type] I agree we sho

Re: Trying to configure bash

On Tue, Feb 6, 2024, at 10:03 AM, Daniel Premo wrote: > I'm guessing there's no C compiler, based on skimming > https://buildroot.org/ and https://www.busybox.net/ . (Spotted > Buildroot in Mainsail and spotted Busybox in the /usr/bin/ folder -- > many of the programs in /usr/bin/ are symlinks to /

Re: Trying to configure bash

On Mon, Feb 5, 2024, at 10:16 PM, Daniel Premo wrote: > root@F005-068E /root/projects/bash/bash-5.2.21 [#] ./configure > checking build system type... ././support/config.guess: unable to guess > system type > > NOTE: MIPS GNU/Linux systems require a C compiler to fully recognize > the system type

Re: Unrecognized system

On Thu, Nov 2, 2023, at 10:13 AM, Piotr Nowicki wrote: > config.guess timestamp = 2003-10-03 > This is 20 years out of date. What are you trying to build? You may need to get a newer version of it. > uname -m = aarch64 > > uname -r = 6.1.0-odroid-arm64 > > uname -s = Linux > This system shou

Re: [PATCH] config.sub: Accept LLVM-style $cpu-$vendor-windows-cygnus

On Mon, Sep 25, 2023, at 10:08 PM, Jacob Bachmeyer wrote: > Zack Weinberg wrote: >> On Thu, Sep 21, 2023, at 9:49 PM, Jacob Bachmeyer wrote: >> >>> I further argue that alternate output modes should only be supported >>> at config.sub; config.guess should

Re: [PATCH 2/3] config.sub: Factor out `invalid_config` function

>> On Mon, Sep 25, 2023, at 10:57 AM, John Cotton Ericson wrote: >>> Sure. If they show up, we can definitely revert it. But what happens >>> if they *don't* show up? What do you think in that case? >>> >> How long are you prepared to stick to your position? How many angry >> e- mails are you prepa

Re: [PATCH 2/3] config.sub: Factor out `invalid_config` function

On Mon, Sep 25, 2023, at 10:57 AM, John Cotton Ericson wrote: > On 9/25/23 10:24, Zack Weinberg wrote: > >> It is ultimately ldv's call, but Jacob's experiment is not good >> enough for me to approve. >> > So I saw Jacob's research as not demonstrating

Re: [PATCH] config.sub: Accept LLVM-style $cpu-$vendor-windows-cygnus

On Thu, Sep 21, 2023, at 9:49 PM, Jacob Bachmeyer wrote: > I further argue that alternate output modes should only be supported > at config.sub; config.guess should always produce the current hyphen- > delimited tuple format. That would preclude autoconf using the new format. We don't want to hav

Re: [PATCH 2/3] config.sub: Factor out `invalid_config` function

On Fri, Sep 22, 2023, at 5:14 PM, John Cotton Ericson wrote: > On 9/21/23 22:31, Jacob Bachmeyer wrote: >> Zack Weinberg wrote: >>> >>> Um. I don't think you can use shell functions in this file (or in >>> config.guess), for the same reason you can't

Re: [PATCH 2/3] config.sub: Factor out `invalid_config` function

On Thu, Sep 21, 2023, at 3:52 PM, John Ericson wrote: ... > # Functions > ### > > +# Invalid configuration; display a message and exit > +# > +# Param 1: configuration > +# Param 2: message > +invalid_config () { > + echo "Invalid configuration '$1': $2" 1>&2 > + exit 1 > +} Um.

Re: [PATCH] config.sub: Accept LLVM-style $cpu-$vendor-windows-cygnus

On Wed, Sep 20, 2023, at 9:59 AM, John Ericson wrote: > On Wed, Sep 20, 2023, at 6:01 AM, Dmitry V. Levin wrote: >> Of course config.sub can provide a canonicalization of windows-cygnus >> into cygwin if it helps. > > I was worried that would close off the possibility of adding them as > normal for

Re: Whither windows-msvc

On Mon, Sep 18, 2023, at 8:02 PM, Po Lu wrote: > linux-musl is so named because there is no canonical name for a > Musl-based Linux system. The "musl" represents "musl-based operating > system", not merely the libc itself. Ditto for ulibc. I'm gonna push back real hard on this specific aspect of

Re: Rethinking configuration tuples

On Sun, Sep 10, 2023, at 10:11 PM, Po Lu wrote: > Where are the config maintainers? Karl Barry and company? (I don't > remember his e-mail nor do I have it at hand.) Karl Berry is the Automake maintainer. I'm not sure if there *is* an official config.* maintainer. The person most appropriately de

Re: Rethinking configuration tuples

I haven't been following this long discussion very closely but I do have some opinions (with my "de facto autoconf maintainer" hat on): 1. As a general rule, it is not safe to change the canonicalization (i.e. the config.sub output) of an existing system name, *at all*; in many cases, not even

Re: config.sub should normalize *-*-windows-*

On Thu, Aug 17, 2023, at 8:34 PM, Po Lu wrote: ... > Given that the MinGW ABI does not constitute the GNU operating system > executing on the MS-Windows kernel, and MSVC is not an operating system, > such blunders should be ignored, or at least normalized... Even more important than this is the pr

Re: Problem in installing risv-tool chain

On Tue, Aug 17, 2021, at 5:22 AM, Thota Yateesh Chandrasai cs19b044 wrote: > #I tries installing riscv-toolchain and this error is popping up every time. > #I am using Ubuntu 20.04 on mac m1 using parllels application. > #I tries to update the config.guess file but the problem didn't change. ... >

Re: [PATCH v2 0/8] restore compatibility with pre-POSIX shells in config.guess

On Wed, May 26, 2021 at 10:42 PM Jacob Bachmeyer wrote: > Jacob Bachmeyer wrote: > > [...] > > Jacob Bachmeyer (8): > > config.guess: use intermediate variable with uname results > > config.guess: manual fixups after previous automatic patch > > config.guess: remove unneeded quotes and facto

Re: [PATCH 0/6] restore compatibility with pre-POSIX shells in config.guess

On Mon, May 24, 2021 at 9:31 PM Jacob Bachmeyer wrote: > Zack Weinberg wrote: > > On Sun, May 23, 2021 at 12:19 AM Jacob Bachmeyer wrote: > >> Zack Weinberg wrote: > >>> “*All* shell variable interpolations will be inside double quotes, > >>> except whe

Re: [PATCH 0/6] restore compatibility with pre-POSIX shells in config.guess

On Sun, May 23, 2021 at 12:19 AM Jacob Bachmeyer wrote: > Zack Weinberg wrote: > > I fully endorse reverting config.{sub,guess} to classic backtick > > command substitutions. > > Thank you for your support. > > > However, Autoconf proper (in 2.70+) will continue to

Re: [PATCH 0/6] restore compatibility with pre-POSIX shells in config.guess

On Sat, May 22, 2021 at 9:06 PM Jacob Bachmeyer wrote: > This patch series tidies config.guess and reverts to classic backtick > command substitutions. I fully endorse reverting config.{sub,guess} to classic backtick command substitutions. However, Autoconf proper (in 2.70+) will continue to lo

Re: [PATCH] config.guess: Fix aarch64 macOS detection with GNU uname

On Tue, Mar 23, 2021 at 8:29 AM m...@diatr.us wrote: > > This is needed on Apple iOS devices. > Compiling on an iPhone or iPad, UNAME_MACHINE is equivalent to the device > model. (e.g. iPhone12,3) To avoid all doubt, could you please copy and paste the output of the appended shell script on an i

Re: configure: error: cannot guess build type; you must specify one

On Sun, Jan 10, 2021 at 4:26 PM David wrote: > This a Raspberry PI 4 with ubuntu server 20.04 installed ... > config.guess timestamp = 2006-07-02 ^^ Your config.guess is nearly 15 years old and understandably does not know about AArch64. Current copies of confi

Re: When running "config.guess" it fails to recognize the operating system. See output in the mail body.

On Mon, Jan 4, 2021 at 7:10 PM Dmitry V. Levin wrote: > On Fri, Jan 01, 2021 at 01:37:32PM -0500, Zack Weinberg wrote: > > On Fri, Jan 1, 2021 at 1:00 PM Alfred M. Szmidt wrote: > > > Markus Fischer wrote: > > >> I had downloaded from > > >> "ht

Re: When running "config.guess" it fails to recognize the operating system. See output in the mail body.

On Fri, Jan 1, 2021 at 1:00 PM Alfred M. Szmidt wrote: > Markus Fischer wrote: >> I had downloaded from >> "http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/config/config/config.guess"; ... > That doesn't correspond to the output you sent; which says that > config.guess is from 2008 -- a very o

Re: PATCH: eliminate backtick substitution

Dmitry V. Levin wrote: >On Tue, Dec 01, 2020 at 04:40:07PM -0700, Karl Berry wrote: >> >> It's time to join the 1990s and replace the backtick substitutions in >> config.guess and config.sub with the $(..) command substitution >> >> I admit I don't understand the reason behind this last cha