From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-220583-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 31687 invoked by alias); 19 Jun 2008 13:01:14 -0000
Received: (qmail 31679 invoked by uid 22791); 19 Jun 2008 13:01:13 -0000
X-Spam-Check-By: sourceware.org
Received: from yx-out-1718.google.com (HELO yx-out-1718.google.com) (74.125.44.158)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 19 Jun 2008 13:00:51 +0000
Received: by yx-out-1718.google.com with SMTP id 36so89310yxh.26         for <gcc-patches@gcc.gnu.org>; Thu, 19 Jun 2008 06:00:49 -0700 (PDT)
Received: by 10.150.196.20 with SMTP id t20mr3140391ybf.99.1213880448315;         Thu, 19 Jun 2008 06:00:48 -0700 (PDT)
Received: by 10.150.137.11 with HTTP; Thu, 19 Jun 2008 06:00:48 -0700 (PDT)
Message-ID: <206fcf960806190600u4be4c1d9x809c4fd5d5531f66@mail.gmail.com>
Date: Thu, 19 Jun 2008 13:05:00 -0000
From: "Gabriel Dos Reis" <gdr@integrable-solutions.net>
To: "Ian Lance Taylor" <iant@google.com>
Subject: Re: gcc-in-cxx branch created
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
In-Reply-To: <m3wsklwr2b.fsf@google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <m363s746yo.fsf@google.com> 	 <206fcf960806190347l5ea21e63reeef116180668402@mail.gmail.com> 	 <m3wsklwr2b.fsf@google.com>
X-Google-Sender-Auth: 3a554f74723c0f00
X-IsSubscribed: yes
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
X-SW-Source: 2008-06/txt/msg01266.txt.bz2

On Thu, Jun 19, 2008 at 7:24 AM, Ian Lance Taylor <iant@google.com> wrote:

>> The reason I'm asking is that a fresh build o gcc-in-cxx dies on my machine with
>> complains that `program' has conflicting declarations: once in
>> libcpp.h as having
>> C++ linkage, once in toplev.h with a C declaration.  It is the
>> tradition in modern
>> C++ to avoid having many `sources' for the same declaration.
>
> Yes.  I'm working around that for now by editing toplev.h, to avoid
> pushing libcpp and libiberty to C++ right away.
>
> #ifdef __cplusplus
> extern "C" {
> #endif
>
> /* This is used by cpplib and libiberty.  */
> extern const char *progname;
>
> #ifdef __cplusplus
> }
> #endif

Yes that makes sense.

>
>
> I'll try to get my current set of patches committed to the branch
> later today.

I'll wait until your patches are in.
Thanks!

-- Gaby