This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/52226] Trunk fails to bootstrap on Mac OS X.
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 13 Feb 2012 11:17:33 +0000
- Subject: [Bug bootstrap/52226] Trunk fails to bootstrap on Mac OS X.
- Auto-submitted: auto-generated
- References: <bug-52226-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52226
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-13 11:17:33 UTC ---
(In reply to comment #3)
> --enable-concept-checks \
You probably don't want this, some of the concept checks are incompatible with
C++11, you shouldn't enable them at configure time, you can still use them
later with -D_GLIBCXX_CONCEPT_CHECKS
> --enable-decimal-float \
> --enable-fully-dynamic-string \
> --enable-libstdcxx-debug \
> --enable-libstdcxx-time \
This implies you want to use C++11, so you probably don't want to permanently
enable concept checks.
> --enable-multilib \
> --enable-plugin \
> --enable-lto \
If your build fails it's usually a good idea to try *removing* options to find
the smallest set that can reproduce the bug, instead you're adding more
options.
> --enable-static \
> --enable-shared \
> --enable-threads \
These are redundant, you're explicitly setting default behaviour.
> --enable-version-specific-runtime-libs
This is broken on x86_64 multilib
I don't think these are the cause of your problem, I just think you'll find it
easier to identify the real problem if you keep it simple instead of adding
loads of unnecessary complication.