public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: Iain Sandoe <idsandoe@googlemail.com>, GCC Development <gcc@gcc.gnu.org>
Subject: Re: remove intl/ directory?
Date: Sun, 19 Jun 2022 02:53:17 +0200	[thread overview]
Message-ID: <5492574.WonRQIJPbA@omega> (raw)
In-Reply-To: <CAGWvnymbMoA+Wp0oPfZKP6O3iDO5vChXMDxmGVCp+GboOO1uVg@mail.gmail.com>

David Edelsohn wrote:
> The broad list of systems supported by GCC requires effort, but is one
> of its advantages.

GNU gettext is supported on a wide list of systems as well. Before we make
a GNU gettext release, we test in on glibc systems, FreeBSD, NetBSD, OpenBSD,
macOS, AIX, Solaris, Cygwin, native Windows systems.

> Making it more difficult to support GCC on
> non-GLIBC systems will be detrimental to GCC.

You appear to be saying that using tested GNU gettext release tarballs will
make it "more difficult" for GCC than to continue to use an old code
from 2003, with occasional backports from upstream. Why?

Bruno




  reply	other threads:[~2022-06-19  0:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18 17:01 Bruno Haible
2022-06-18 17:42 ` Iain Sandoe
2022-06-18 18:14   ` David Edelsohn
2022-06-19  0:53     ` Bruno Haible [this message]
2022-06-19  0:32   ` Bruno Haible
2022-06-19  8:40     ` Iain Sandoe
2022-06-19 20:15       ` Iain Sandoe
2022-06-21  2:05         ` Bruno Haible
2022-06-22 20:21           ` Iain Sandoe
2022-06-23  4:24             ` Bruno Haible
2022-06-23  6:51               ` Iain Sandoe
2022-06-23 15:40                 ` Iain Sandoe
2022-06-23 15:50                   ` Iain Sandoe
2022-06-23 15:13               ` Eric Gallager
2022-06-20 19:45 ` Eric Gallager
2022-06-21  2:09   ` Bruno Haible

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=5492574.WonRQIJPbA@omega \
    --to=bruno@clisp.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=idsandoe@googlemail.com \
    /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).