This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Document use of CC and CFLAGS in more detail (bug 20980, bug 21234)
- From: Rical Jasan <ricaljasan at pacific dot net>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 15 Feb 2018 20:50:01 -0800
- Subject: Re: Document use of CC and CFLAGS in more detail (bug 20980, bug 21234)
- Authentication-results: sourceware.org; auth=none
- References: <alpine.DEB.2.20.1802012037260.13065@digraph.polyomino.org.uk>
On 02/01/2018 12:37 PM, Joseph Myers wrote:
...
> diff --git a/manual/install.texi b/manual/install.texi
> index efcd986..5cf8e16 100644
> --- a/manual/install.texi
> +++ b/manual/install.texi
> @@ -59,10 +59,17 @@ but the normal setting to install as the standard system library is
> @samp{--prefix=/usr} for @gnulinuxsystems{} and @samp{--prefix=} (an
> empty prefix) for @gnuhurdsystems{}.
>
> -It may also be useful to set the @var{CC} and @var{CFLAGS} variables in
> -the environment when running @code{configure}. @var{CC} selects the C
> -compiler that will be used, and @var{CFLAGS} sets optimization options
> -for the compiler.
> +It may also be useful to pass @samp{CC=@var{compiler}} and
Is this a rogue @samp here, or was that intentional (everywhere else is
@code)?
Otherwise, I think this patch achieves the goal of more explicitly
documenting expected usage of CC and CFLAGS. (I see it's been
committed, but hopefully an additional ACK doesn't hurt. :)
Rical