This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: linking problem when using "fopen"
- From: Robin Farine <robin dot farine at acn-group dot ch>
- To: jyl087 at netscape dot net
- Cc: eCos users <ecos-discuss at sources dot redhat dot com>
- Date: 02 Apr 2002 08:47:57 +0200
- Subject: Re: [ECOS] linking problem when using "fopen"
- References: <4DDD85A0.0AA70F0A.00067016@netscape.net>
On Tue, 2002-04-02 at 00:13, jyl087@netscape.net wrote:
> When I use the "fopen" call in my eCos application, I have problems
> with linking. It seems that when "fopen_inner" calls "new Cyg_StdioStream"
> it drags in all kinds of C++ exception handling cruft. I've verified
> that fopen.cxx was compiled with "-fno_rtti -fno_exceptions", but
> for some reason, the "new" call drags in all the RTTI and exception
> handling stuff.
>
> I've verified that by commenting out the "new Cyg_StdioStream" call in
> "fopen_inner" in the "fopen.cxx" file, my link errors go away, but
> obviously fopen no longer works.
>
> Any ideas?
Using the non-throwing form of operator new might work:
new (std::nothrow) Cyg_StdioStream(...);
Robin
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss