public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/61315] wide-int.cc cannot be built by darwin system compiler
Date: Mon, 26 May 2014 09:08:00 -0000	[thread overview]
Message-ID: <bug-61315-4-HxC72qAPKJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61315-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61315

Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
   Last reconfirmed|                            |2014-05-26
         Resolution|INVALID                     |---
     Ever confirmed|0                           |1

--- Comment #2 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
GCC fails to build on a secondary target, with its default configuration.
Wherever the bug is, does not change the fact that GCC should work around it
one way or another, as it does work around many build/host/target bugs through
configury.

Even if a decision is made to drop darwin as a secondary target, this would
remain at the very least a documentation bug. Both Marc Glisse and I suggest
this is more serious than you think, so please leave it open at least til a
maintainer can get a look at it.


  parent reply	other threads:[~2014-05-26  9:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  8:08 [Bug bootstrap/61315] New: " fxcoudert at gcc dot gnu.org
2014-05-26  9:00 ` [Bug bootstrap/61315] " pinskia at gcc dot gnu.org
2014-05-26  9:08 ` fxcoudert at gcc dot gnu.org [this message]
2014-05-26  9:11 ` pinskia at gcc dot gnu.org
2014-05-26  9:21 ` fxcoudert at gcc dot gnu.org
2014-05-27 16:21 ` howarth at nitro dot med.uc.edu
2014-05-27 16:35 ` howarth at nitro dot med.uc.edu
2014-05-27 18:01 ` dominiq at lps dot ens.fr
2014-05-27 18:26 ` pinskia at gcc dot gnu.org
2014-05-27 19:15 ` howarth at nitro dot med.uc.edu
2014-05-27 20:36 ` mrs at gcc dot gnu.org
2014-05-28  7:57 ` manu at gcc dot gnu.org
2014-05-28 10:18 ` dominiq at lps dot ens.fr
2014-05-28 11:21 ` manu at gcc dot gnu.org
2014-06-03 16:19 ` joseph at codesourcery 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-61315-4-HxC72qAPKJ@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).