public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Neyman <noreply@github.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] bd0ea7: prevent the glibc build from overwriting flags
Date: Sun, 16 Feb 2020 23:22:00 -0000	[thread overview]
Message-ID: <crosstool-ng/crosstool-ng/push/refs/heads/master/489742-4fa0ba@github.com> (raw)

  Branch: refs/heads/master
  Home:   https://github.com/crosstool-ng/crosstool-ng
  Commit: bd0ea7ed21f140d4e911ff4a63693b54a455c349
      https://github.com/crosstool-ng/crosstool-ng/commit/bd0ea7ed21f140d4e911ff4a63693b54a455c349
  Author: Norbert Lange <nolange79@gmail.com>
  Date:   2019-10-27 (Sun, 27 Oct 2019)

  Changed paths:
    M scripts/build/libc/glibc.sh

  Log Message:
  -----------
  prevent the glibc build from overwriting flags

The glibc will append the content of the CFLAGS variable,
overriding previous flags.
If unset, the CFLAGS variable is not empty, so explicitly set it.
Instead prepend the default CFLAGS flags.

Signed-off-by: Norbert Lange <nolange79@gmail.com>


  Commit: 4fa0ba100b8924b27942ff253c5474c655427027
      https://github.com/crosstool-ng/crosstool-ng/commit/4fa0ba100b8924b27942ff253c5474c655427027
  Author: Alexey Neyman <stilor@att.net>
  Date:   2020-02-16 (Sun, 16 Feb 2020)

  Changed paths:
    M scripts/build/libc/glibc.sh

  Log Message:
  -----------
  Merge pull request #1270 from nolange/prevent_glibc_cflags_override

prevent the glibc build from overwriting flags


Compare: https://github.com/crosstool-ng/crosstool-ng/compare/4897426202e5...4fa0ba100b89

                 reply	other threads:[~2020-02-16 23:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=crosstool-ng/crosstool-ng/push/refs/heads/master/489742-4fa0ba@github.com \
    --to=noreply@github.com \
    --cc=crossgcc@sourceware.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).