X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
Date: Wed, 10 Apr 2002 15:20:14 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: making dxe2gen with clio.rice.edu binaries -or- "undefined reference to 'operator'"?
In-Reply-To: <a90vct$t5q$1@nets3.rz.RWTH-Aachen.DE>
Message-ID: <Pine.SUN.3.91.1020410151821.24008C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 10 Apr 2002, Hans-Bernhard Broeker wrote:

> Hmm... yes, looks like it (tested with GCC-2.95.2 on Linux).  I'm
> surprised.  I was pretty certain that if you did linking and
> compilation in one go, gcc recognized that the source file(s) are in
> C++, so the C++ runtime should be linked in automatically.

It can't do that, except in a small number of very specific and rare 
cases (where all the files are compiled and linked in one go).  The 
reason is that the object file normally doesn't carry any information 
about the source language, at least with most debug info formats.

Since most of the programs are linked from object files that were 
compiled in a separate run, the special case where GCC could do this is 
very unimportant.