Hi Iain,

Iain Sandoe <i...@sandoe.co.uk> writes:

> Hi Arsen,
>
>> On 28 Oct 2023, at 10:22, Arsen Arsenović <ar...@aarsen.me> wrote:
>
>> Andrew Pinski <pins...@gmail.com> writes:
>> 
>>> One comment from me. It would be nice to update install.texi in
>>> gcc/doc/ to make a mention of this requirement for non-glibc hosts.
>> 
>> What do you think of the following:
>
> The hiccup for me is that we need to mention that libintl is provided by a 
> package
> with a different name, that might not be obvious to someone unfamiliar with 
> this.

I'll throw in "provided by GNU gettext"

>> 
>> 
>> diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
>> index a17016cd8977..e5137f9d7a1b 100644
>> --- a/gcc/doc/install.texi
>> +++ b/gcc/doc/install.texi
>> @@ -2215,6 +2215,11 @@ which lets GCC output diagnostics in languages other 
>> than American
>> English.  Native Language Support is enabled by default if not doing a
>> canadian cross build.  The @option{--disable-nls} option disables NLS@.
>> 
>> +Note that this functionality requires either libintl or C standard
>> +library that contains support for gettext (such as the GNU C Library).
> s/gettext/NLS/

Hmm, I was referring to the library function here, which matches the
table this sentence references (which names a column 'gettext present in
libc').

> +If your installation does not provide either, libibtl can be provided by the 
> gettext package 
>> +@xref{with-included-gettext,,--with-included-gettext} for more
> “see …"

@xref inserts 'See '
>> +information on the conditions required to get gettext support.
>
> information on the options for providing gettext {as part of the
> build?}

The table is more general.  It covers what happens with/without gettext
in-tree, with/without libintl on the system, with/without gettext in
libc and when passing --with/out-included-gettext.

Thanks, have a lovely day.
-- 
Arsen Arsenović

Attachment: signature.asc
Description: PGP signature

Reply via email to