public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] a50577: gcc: Fix CC_GCC_ENABLE_CXX_FLAGS for mode=baremeta...
Date: Wed, 06 Jan 2016 19:25:00 -0000	[thread overview]
Message-ID: <568d6a11c58c5_337f3fb30fc8f29c799a2@hookshot-fe5-cp1-prd.iad.github.net.mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

  Branch: refs/heads/master
  Home:   https://github.com/crosstool-ng/crosstool-ng
  Commit: a5057713a0394d189adc8b9abb0eb65592ecfc49
      https://github.com/crosstool-ng/crosstool-ng/commit/a5057713a0394d189adc8b9abb0eb65592ecfc49
  Author: Bryan Hundven <bryanhundven@gmail.com>
  Date:   2016-01-06 (Wed, 06 Jan 2016)

  Changed paths:
    M scripts/build/cc/100-gcc.sh

  Log Message:
  -----------
  gcc: Fix CC_GCC_ENABLE_CXX_FLAGS for mode=baremetal

When creating a baremetal toolchain, CC_GCC_ENABLE_CXX_FLAGS has no
effect. This closes #298

Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>


  Commit: f72bd213890b4ff3e1a96a6d4831829bdb7bc0e3
      https://github.com/crosstool-ng/crosstool-ng/commit/f72bd213890b4ff3e1a96a6d4831829bdb7bc0e3
  Author: Bryan Hundven <bryanhundven@gmail.com>
  Date:   2016-01-06 (Wed, 06 Jan 2016)

  Changed paths:
    M scripts/build/cc/100-gcc.sh

  Log Message:
  -----------
  Merge pull request #314 from bhundven/fix_enable_cxx_flags_baremetal

gcc: Fix CC_GCC_ENABLE_CXX_FLAGS for mode=baremetal


Compare: https://github.com/crosstool-ng/crosstool-ng/compare/7aff139719dc...f72bd213890b

[-- Attachment #2: Type: text/plain, Size: 71 bytes --]

--
For unsubscribe information see http://sourceware.org/lists.html#faq

                 reply	other threads:[~2016-01-06 19:25 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=568d6a11c58c5_337f3fb30fc8f29c799a2@hookshot-fe5-cp1-prd.iad.github.net.mail \
    --to=bryanhundven@gmail.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).