public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/60348] -static-libstdc++ broken
Date: Thu, 27 Feb 2014 16:00:00 -0000	[thread overview]
Message-ID: <bug-60348-4-tIeduXJbHq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60348-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60348

--- Comment #16 from Andreas Schwab <schwab@linux-m68k.org> ---
If you want to build for old systems you need to use the old tools from those
old systems and the output will still work on newer systems (backward
compatiblity).  New tools are using new features as they are available (no
forward compatibility).


  parent reply	other threads:[~2014-02-27 16:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 19:27 [Bug libstdc++/60348] New: " nachms+gcc at gmail dot com
2014-02-27  9:04 ` [Bug libstdc++/60348] " rguenth at gcc dot gnu.org
2014-02-27 11:02 ` nachms+gcc at gmail dot com
2014-02-27 11:59 ` glisse at gcc dot gnu.org
2014-02-27 12:43 ` nachms+gcc at gmail dot com
2014-02-27 13:16 ` glisse at gcc dot gnu.org
2014-02-27 13:31 ` nachms+gcc at gmail dot com
2014-02-27 13:44 ` nachms+gcc at gmail dot com
2014-02-27 14:11 ` glisse at gcc dot gnu.org
2014-02-27 14:37 ` rguenth at gcc dot gnu.org
2014-02-27 14:59 ` nachms+gcc at gmail dot com
2014-02-27 15:04 ` rguenth at gcc dot gnu.org
2014-02-27 15:43 ` nachms+gcc at gmail dot com
2014-02-27 15:50 ` rguenth at gcc dot gnu.org
2014-02-27 15:56 ` nachms+gcc at gmail dot com
2014-02-27 15:58 ` rguenth at gcc dot gnu.org
2014-02-27 16:00 ` schwab@linux-m68k.org [this message]
2014-02-27 16:14 ` nachms+gcc at gmail dot com

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=bug-60348-4-tIeduXJbHq@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).