This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: linking problem when using "fopen"


Robin Farine wrote:
> 
> 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(...);

I'm afraid I doubt this will work.

What C++ cruft does it pull in that causes a problem?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]