public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Minor update to installation docs
Date: Wed, 1 Nov 2023 23:11:47 +0100 (CET)	[thread overview]
Message-ID: <41eb2189-57c4-a6a1-765f-09d4e5f4275a@pfeifer.com> (raw)
In-Reply-To: <20230918111807.2453946-1-jwakely@redhat.com>

On Mon, 18 Sep 2023, Jonathan Wakely via Gcc-patches wrote:
> @@ -103,8 +103,10 @@ ln -s libiconv-1.16 libiconv
>  	<para>
>  	  If GCC 3.1.0 or later on is being used on GNU/Linux, an attempt
>  	  will be made to use "C" library functionality necessary for
> -	  C++ named locale support.  For GCC 4.6.0 and later, this
> -	  means that glibc 2.3 or later is required.
> +	  C++ named locale support, e.g. the <function>newlocale</function>
> +	  and <function>uselocale</function> functions.
> +	  For GCC 4.6.0 and later,
> +	  this means that glibc 2.3 or later is required.

Do we still need to provide those details on GCC 3.1+ and GCC 4.6+?

Would it make sense to simply require glibc 2.3 (or higher)?

Gerald

  reply	other threads:[~2023-11-01 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 11:17 Jonathan Wakely
2023-11-01 22:11 ` Gerald Pfeifer [this message]
2023-11-02 11:04   ` Jonathan Wakely

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=41eb2189-57c4-a6a1-765f-09d4e5f4275a@pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    /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).