public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63773] [meta-bug] Restoring darwin bootstrap for gcc 5.0 Date: Tue, 11 Nov 2014 20:59:00 -0000 [thread overview] Message-ID: <bug-63773-4-HWVxp70iyO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63773 --- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Francois-Xavier Coudert from comment #14) > (In reply to Dominique d'Humieres from comment #13) > > There is still a bootstrapping issue with libcc1 when bootstrapping with gcc > > 4.9: > > Regarding that one, it should be fixed in the top-level Makefile. The > targets that configure and build libcc1 in this Makefile call > $(HOST_EXPORTS), which should do the trick. Instead, it should probably do > like lto, and use $(HOST_EXPORTS) and $(POSTSTAGE1_HOST_EXPORTS) together > for stages > 1. ACK - I think that's completely the right approach to one part of the problem. - what's happening is that the analysis for the _bootstrap_ compiler's support of the -static-libstdc++ is being used for the _stage#3_ build of libcc1 for clang [bootstrap] -static-libstdc++ is not supported and thus libcc1 links with /usr/lib/libstdc++.dylib (which is not really what was intended). for gcc [bootstrap] the support is mentioned - and then the -static-libstdc++ flag is provided to the libcc1 link (which then fails with…). … the second issue - which is that we need a -B…. option for each library path that will be used for spec-substitution (.a for .dylib). so we need -B/path/to/libstdc++-v3/src/.libs and -B/path/to/libsupc++/.libs,. > > Looking at Makefile.def, the only difference I see is that libcc1 is not > bootstrapped, so maybe we could fix it this way? > > Index: Makefile.def > =================================================================== > --- Makefile.def (revision 217355) > +++ Makefile.def (working copy) > @@ -123,7 +123,8 @@ host_modules= { module= gnattools; }; > host_modules= { module= lto-plugin; bootstrap=true; > extra_configure_flags='--enable-shared @extra_linker_plugin_flags@ > @extra_linker_plugin_configure_flags@'; > extra_make_flags='@extra_linker_plugin_flags@'; }; > -host_modules= { module= libcc1; extra_configure_flags=--enable-shared; }; > +host_modules= { module= libcc1; bootstrap=true; > + extra_configure_flags=--enable-shared; }; > > target_modules = { module= libstdc++-v3; > bootstrap=true; I don't think we want to bootstrap libcc1 (that was what the patch was removing). Probably the right example is gnattools - or something similar that only builds @stage#3. >From gcc-bugs-return-466438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Nov 11 21:09:09 2014 Return-Path: <gcc-bugs-return-466438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 23140 invoked by alias); 11 Nov 2014 21:09:09 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 22816 invoked by uid 48); 11 Nov 2014 21:09:04 -0000 From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/63825] [DR 1558] Unused arguments in alias template specializations Date: Tue, 11 Nov 2014 21:09:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-63825-4-6OH1hFsiDm@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-63825-4@http.gcc.gnu.org/bugzilla/> References: <bug-63825-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-11/txt/msg00910.txt.bz2 Content-length: 174 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc825 --- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> --- Doh, works for me too if I use a fresh build - thanks!
next prev parent reply other threads:[~2014-11-11 20:59 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-07 17:31 [Bug target/63773] New: " howarth at bromo dot med.uc.edu 2014-11-07 17:39 ` [Bug target/63773] " dominiq at lps dot ens.fr 2014-11-07 21:06 ` evstupac at gmail dot com 2014-11-07 21:24 ` fxcoudert at gcc dot gnu.org 2014-11-07 22:24 ` fxcoudert at gcc dot gnu.org 2014-11-07 22:38 ` howarth at bromo dot med.uc.edu 2014-11-07 23:07 ` fxcoudert at gcc dot gnu.org 2014-11-08 2:47 ` howarth at bromo dot med.uc.edu 2014-11-08 10:12 ` howarth at bromo dot med.uc.edu 2014-11-09 5:34 ` howarth at bromo dot med.uc.edu 2014-11-11 10:18 ` fxcoudert at gcc dot gnu.org 2014-11-11 15:28 ` dominiq at lps dot ens.fr 2014-11-11 20:47 ` fxcoudert at gcc dot gnu.org 2014-11-11 20:59 ` iains at gcc dot gnu.org [this message] 2014-11-11 21:09 ` fxcoudert at gcc dot gnu.org 2014-11-11 22:09 ` howarth at bromo dot med.uc.edu 2014-11-15 12:18 ` fxcoudert at gcc dot gnu.org 2014-11-20 11:22 ` fxcoudert at gcc dot gnu.org 2014-11-25 21:55 ` fxcoudert at gcc dot gnu.org 2014-12-14 22:56 ` dominiq at lps dot ens.fr 2014-12-19 13:51 ` trippels 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-63773-4-HWVxp70iyO@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: linkBe 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).