public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/67066] libstdc++-v3/src/filesystem/dir.cc fails to compile, preventing bootstrapping with libstdcxx-filesystem-ts
Date: Thu, 30 Jul 2015 16:52:00 -0000	[thread overview]
Message-ID: <bug-67066-4-hdpnHuOKS7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67066-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Are you playing "use as many configure options as possible"?

Most of those options are on by default anyway, others don't do anything.

I'm pretty sure --enable-libstdcxx-time is redundant on darwin.

--enable-multiarch is for Debian

Where did you get that command, and if it's causing so much trouble why not try
simplifying it?


  parent reply	other threads:[~2015-07-30 16:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 13:49 [Bug bootstrap/67066] New: " egall at gwmail dot gwu.edu
2015-07-30 13:55 ` [Bug bootstrap/67066] " egall at gwmail dot gwu.edu
2015-07-30 16:50 ` redi at gcc dot gnu.org
2015-07-30 16:52 ` redi at gcc dot gnu.org [this message]
2015-07-30 17:14 ` [Bug libstdc++/67066] libstdc++-v3/src/filesystem/dir.cc fails to compile with --enable-concept-checks redi at gcc dot gnu.org
2015-07-30 18:41 ` egall at gwmail dot gwu.edu
2015-08-18 18:05 ` redi at gcc dot gnu.org
2015-08-18 18:35 ` redi at gcc dot gnu.org
2015-08-28  9:31 ` redi 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-67066-4-hdpnHuOKS7@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).