public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/52509] New: target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)
Date: Tue, 06 Mar 2012 12:33:00 -0000	[thread overview]
Message-ID: <bug-52509-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 52509
           Summary: target libstdc++-v3 should not be bootstrapped,
                    libstdc++-v3 should also be a host_module
                    (bootstrapped)
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rguenth@gcc.gnu.org


We should not need to bootstrap the target libstdc++ (and it's multilibs),
but we only need a host libstdc++ (of the host multilib variant - does
a canadian cross even work right now with C++ bootstrap?).  The host libstdc++
should be a static library only, and it should not build PCH files
(configured with --disable-libstdcxx-pch).

Thus, like simply

Index: Makefile.def
===================================================================
--- Makefile.def        (revision 184981)
+++ Makefile.def        (working copy)
@@ -84,6 +84,8 @@ host_modules= { module= libdecnumber; bo
 host_modules= { module= libgui; };
 host_modules= { module= libiberty; bootstrap=true;
               
extra_configure_flags='@extra_host_libiberty_configure_flags@';};
+host_modules= { module= libstdc++-v3; bootstrap=true;
+               extra_configure_flags='--disable-libstdcxx-pch';}
 // We abuse missing to avoid installing anything for libiconv.
 host_modules= { module= libiconv;
                extra_configure_flags='--disable-shared';
@@ -113,7 +115,6 @@ host_modules= { module= lto-plugin; boot
                extra_configure_flags=--enable-shared; };

 target_modules = { module= libstdc++-v3;
-                  bootstrap=true;
                   lib_path=src/.libs;
                   raw_cxx=true; };
 target_modules = { module= libmudflap; lib_path=.libs; };

?


             reply	other threads:[~2012-03-06 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 12:33 rguenth at gcc dot gnu.org [this message]
2012-03-06 12:59 ` [Bug bootstrap/52509] " jakub at gcc dot gnu.org
2012-03-06 13:16 ` rguenth at gcc dot gnu.org
2012-03-06 13:32 ` jakub 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-52509-4@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).