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: compile error using 3.2 MIPS using std name spaces


Attached is the  preprocess the file, the way it looks to me "new" is
defined i.e. not included, thus treating the operator as a simple function.
The files have not been modified, could it be something with a include not
being setup correctly?

Thoughts?

I'm using the net_new template and month old CVS archive of ecos  and just
creating a standard build. I also, recreated this building a new_net build.

----- Original Message -----
From: "Jonathan Larmour" <jifl@eCosCentric.com>
To: "Tim Michals" <t.michals@attbi.com>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Wednesday, January 15, 2003 8:35 AM
Subject: Re: [ECOS] compile error using 3.2 MIPS using std name spaces


> Tim Michals wrote:
> > Problem:
> > Compiling the posix, I'm getting this general error:
> > make: Leaving directory `/ecos-c/mips/acacia/ecos/applib/applib_build'
> > <internal>: In function `void* mq_open(const char*, int, ...)':
> > <internal>:305: too many arguments to function `void* operator
new(unsigned
> > int)'
> > /ecos-c/mips/ecos/packages/compat/posix/current/src/mqueue.cxx:305: at
this
> > point in file
> > /ecos-c/mips/ecos/packages/compat/posix/current/src/mqueue.cxx:685:26:
> > warning: multi-line string literals are deprecated
> > /ecos-c/mips/ecos/packages/compat/posix/current/src/mqueue.cxx:772:26:
> > warning: multi-line string literals are deprecated
> > make[1]: *** [src/mqueue.o.d] Error 1
> > make: *** [build] Error 2
> >
> > This is in reguards to In mqueue.cxx: line 82
> > #include <new>                       // C++ new
> > Not finding the correct name space?
>
> The multi-line string literals warning sits oddly with that. By any chance
> have you #defined malloc to something else in a header?
>
> Can you preprocess the file and see what the new call in mq_open looks
> like then? The easiest way to do this is to repeat the compile line with
> --save-temps and then look at the .i file in the build directory.
>
> Jifl
> --
> eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
> --[ "You can complain because roses have thorns, or you ]--
> --[  can rejoice because thorns have roses." -Lincoln   ]-- 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]