public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][DOCS] Remove install-old.texi
Date: Tue, 18 May 2021 20:18:42 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2105182015580.4027089@digraph.polyomino.org.uk> (raw)
In-Reply-To: <34ce20bc-2529-808a-9862-7f6bcbbb44e6@suse.cz>

On Tue, 18 May 2021, Martin Liška wrote:

> +@quotation
> +aix7.1, aix7.2, amdhsa, androideabi, aout, cygwin, darwin, darwin10, darwin7,
> +darwin8, darwin9, eabi, eabialtivec, eabisim, eabisimaltivec, elf, elf32,
> +elfbare, elfoabi, freebsd4, freebsd6, gnu, hpux, hpux10.1, hpux11.0, hpux11.3,
> +hpux11.9, linux, linux_altivec, lynxos, mingw32, mingw32crt, mmixware, msdosdjgpp,
> +musl, netbsd, netbsdelf, netbsdelf9, none, openbsd, qnx, rtems, solaris2.11,
> +symbianelf, tpf, uclibc, uclinux, uclinux_eabi, vms, vxworks, vxworksae,
> +vxworksmils
> +@end quotation

I'm not sure where this list comes from, but I'd expect "linux" to be the 
canonical "linux-gnu", along with "linux-uclibc", "linux-android", 
"linux-musl" ("uclibc" etc. aren't system names on their own) and variants 
with "eabi" or "eabihf" on the end (see what config.guess produces for 
Arm).

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2021-05-18 20:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 10:59 Martin Liška
2021-05-17 18:38 ` Richard Sandiford
2021-05-17 22:30 ` Joseph Myers
2021-05-18  9:59   ` Martin Liška
2021-05-18 20:18     ` Joseph Myers [this message]
2021-05-19 12:52       ` Martin Liška
2021-05-19 14:49         ` Joseph Myers
2021-05-21  9:11           ` Martin Liška
2021-05-24 20:09             ` Joseph Myers
2021-05-25  8:28               ` Martin Liška
2021-05-25 19:50                 ` Joseph Myers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2105182015580.4027089@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mliska@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).