public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Arnaud Charlet <charlet@adacore.com>
Cc: Laurent GUERBY <laurent@guerby.net>,
	Ian Lance Taylor <iant@google.com>,
	gcc@gcc.gnu.org, Toon Moene <toon@moene.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: C++ bootstrap of GCC - still useful ?
Date: Tue, 12 Jul 2011 08:01:00 -0000	[thread overview]
Message-ID: <201107120953.40626.ebotcazou@adacore.com> (raw)
In-Reply-To: <20110712065417.GA64529@adacore.com>

> Right, we definitely don't want to use the C++ compiler for building the
> Ada run-time.

OK, so the only needed Makefile change is to gcc-interface/Make-lang.in:

Index: ada/gcc-interface/Make-lang.in
===================================================================
--- ada/gcc-interface/Make-lang.in	(revision 176072)
+++ ada/gcc-interface/Make-lang.in	(working copy)
@@ -104,7 +104,7 @@ ADA_TOOLS_FLAGS_TO_PASS=\
 	"GNATLINK=../../gnatlink"	\
 	"GNATBIND=../../gnatbind"
 
-GCC_LINK=$(CC) -static-libgcc $(LDFLAGS)
+GCC_LINK=$(LINKER) $(ALL_LINKERFLAGS) -static-libgcc $(LDFLAGS)
 
 # Lists of files for various purposes.
 

I'm not sure about the long-term interaction with -static-libgcc here, but this 
works currently on Linux so let's keep it for now.

And this means that the initial version adds superfluous extern "C" blocks, I'm 
going to clean it up.

-- 
Eric Botcazou

  parent reply	other threads:[~2011-07-12  7:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-09 20:08 Toon Moene
2011-07-09 22:05 ` Gabriel Dos Reis
2011-07-09 22:27 ` Hargett, Matt
2011-07-10  4:46 ` Ian Lance Taylor
2011-07-10  7:52   ` Eric Botcazou
2011-07-11 16:47     ` Ian Lance Taylor
2011-07-11 16:53       ` Arnaud Charlet
2011-07-11 16:59         ` Paul Koning
2011-07-11 17:28         ` Gabriel Dos Reis
2011-07-11 19:00       ` Eric Botcazou
2011-07-11 20:12         ` Ian Lance Taylor
2011-07-11 20:25           ` Eric Botcazou
2011-07-11 20:58             ` Ian Lance Taylor
2011-07-11 21:12               ` Eric Botcazou
2011-07-11 22:54               ` Laurent GUERBY
2011-07-12  6:47                 ` Eric Botcazou
2011-07-12  6:54                   ` Arnaud Charlet
2011-07-12  7:44                     ` Paolo Bonzini
2011-07-12  7:51                       ` Paolo Bonzini
2011-07-12  8:02                       ` Eric Botcazou
2011-07-12  8:24                         ` Paolo Bonzini
2011-07-12  8:44                           ` Eric Botcazou
2011-07-12  8:21                       ` Arnaud Charlet
2011-07-12  8:01                     ` Eric Botcazou [this message]
2011-07-12 10:57                     ` Paul Koning
2011-07-12 10:58                       ` Arnaud Charlet
2011-07-12 11:11                         ` Paul Koning
2011-07-10 18:03   ` Toon Moene
2011-07-10 18:09     ` Gabriel Dos Reis
2011-07-10 21:21     ` Laurent GUERBY
2011-07-11 18:31       ` Toon Moene

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=201107120953.40626.ebotcazou@adacore.com \
    --to=ebotcazou@adacore.com \
    --cc=charlet@adacore.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=laurent@guerby.net \
    --cc=pbonzini@redhat.com \
    --cc=toon@moene.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).