This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug libc/20980] CFLAGS environment variable replaces vital options


https://sourceware.org/bugzilla/show_bug.cgi?id=20980

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  db9881ecd7e7278af3e6bb252a0b3015e275d7bd (commit)
      from  3785b31c16a507538a9f67f20c75b8a1dfe9939a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=db9881ecd7e7278af3e6bb252a0b3015e275d7bd

commit db9881ecd7e7278af3e6bb252a0b3015e275d7bd
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Thu Feb 15 23:48:47 2018 +0000

    Document use of CC and CFLAGS in more detail (bug 20980, bug 21234).

    There are some bug reports from people setting CFLAGS not including a
    -O option and then being confused when the build fails.  This patch
    addresses this by documenting the proper use of CC and CFLAGS in more
    detail - saying what options should go where and specifying the
    requirement to compile with optimization.

    The previous text incorrectly used @var markup with CC and CFLAGS.
    The correct markup for environment variables is @env, but it's also
    the case that passing such variables explicitly on the configure
    command line is preferred to passing them in the environment, so this
    patch changes the documentation to describe passing them on the
    command line (and uses @code).

    In many cases putting options in the wrong place may in fact work, but
    I believe what I've specified is the correct rule for which options to
    put where.

        [BZ #20980]
        [BZ #21234]
        * manual/install.texi (Configuring and compiling): Describe
        passing CC and CFLAGS on configure command line, not as
        environment variables.  Use @code markup on those variables.
        Specify what options go in CC and what go in CFLAGS.  Note the
        requirement to compile with optimization.
        * INSTALL: Regenerated.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog           |    9 +++++++++
 INSTALL             |   19 ++++++++++++++-----
 manual/install.texi |   25 ++++++++++++++++++-------
 3 files changed, 41 insertions(+), 12 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]