Date:	Fri, 15 Oct 1999 09:59:35 +0300 (WET)
From:	Andris Pavenis <pavenis AT ieva01 DOT lanet DOT lv>
To:	Chris Scaife <scaife AT joltswift DOT freeserve DOT co DOT uk>
cc:	djgpp AT delorie DOT com
Subject:	Re: where does _eh.o come from ?
In-Reply-To:	<7u52gk$9kd$1@news8.svr.pol.co.uk>
Message-ID:	<Pine.A41.4.05.9910150959000.68144-100000@ieva01.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Thu, 14 Oct 1999, Chris Scaife wrote:

> Hi,
> 
> I'm trying to use C++ in an embeded app
> and need to get rid of all file i/o...
> 
> Apparently there is a module libgcc2.c that produced
> a module named _eh.o (quite probably the error handler ?)
> in libgcc.a that invokes fprintf, but I can't
> find it's source file in lgpp2811s.zip
> 
> Am I looking in the wrong place ?
> If you can tell me where to look I would much
> appreciate it :-)
> 

it's in libgcc.a. 

Try compiling with options -fno-exceptions -fno-rtti

- Raw text -