Date: Mon, 15 Dec 1997 10:34:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: DJ Delorie <dj AT delorie DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Trouble with C++ and interrupt (fwd)
In-Reply-To: <199712142115.QAA02758@delorie.com>
Message-ID: <Pine.SUN.3.91.971215103351.22478F-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 14 Dec 1997, DJ Delorie wrote:

> I was thinking of two hacks:
> 
> 1. Modify ld to print "You probably should use gxx, or link with
>    -lstdcxx" if it detects that "cout" or "cin" are one of the undefined
>    symbols.
> 
> 2. If cpp can't find stdio.h, verify the djgpp environment variable
>    points to a real file, and mention that djdev*.zip should be
>    installed.

That's okay, but if gcc could be told via lib/specs to automatically
scan libiostreams and libstdcxx for C++ programs, it would solve the
problem more cleanly in the case where they at least knew to give
their sources the right extensions.  Many DOS-rooted people clearly
expect the C++ libraries to be scanned automatically for them.  Doing
this for the non-LGPL'ed libraries shouldn't harm anybody.

It seems that something like %{.cc: -lstdcxx -liostream} (and the same
for other C++ suffixes) in the "*link_command:" section should do the
job.