public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "prosfilaes at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56752] GCC fails to bootstrap on Debian GNU/Linux 7.0 (wheezy) when x32 libraries aren't installed
Date: Wed, 27 Mar 2013 10:55:00 -0000	[thread overview]
Message-ID: <bug-56752-4-ehtEtsLscK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56752-4@http.gcc.gnu.org/bugzilla/>


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

David Starner <prosfilaes at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |

--- Comment #2 from David Starner <prosfilaes at gmail dot com> 2013-03-27 10:55:02 UTC ---
I don't understand how "that's the way it always has been" is an answer. If
there's a library missing (especially one the installation instructions don't
mention), it should tell you that, not fail in the middle with an obscure error
message. That it has done in it in the past doesn't justify the behavior.


  parent reply	other threads:[~2013-03-27 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 10:32 [Bug bootstrap/56752] New: " prosfilaes at gmail dot com
2013-03-27 10:42 ` [Bug bootstrap/56752] " rguenth at gcc dot gnu.org
2013-03-27 10:55 ` prosfilaes at gmail dot com [this message]
2013-03-27 11:00 ` redi at gcc dot gnu.org
2013-03-27 11:08 ` [Bug bootstrap/56752] GCC fails to bootstrap on Debian GNU/Linux 7.0 (wheezy) when 32-bit " redi at gcc dot gnu.org
2013-03-29 10:00 ` prosfilaes at gmail dot com
2021-07-19  6:10 ` pinskia at gcc dot gnu.org
2021-07-19  6:12 ` pinskia at gcc dot gnu.org

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-56752-4-ehtEtsLscK@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).