This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: thread enabled ecos support


Thank you,

After some reading of configure and make files I figured out how to do it.
I made a base ecos configuration and generated the header files I needed. Then I avoided using the --with-newlib.
When using --with-sysroot option I was able to get it to use errno properly. i also got it using the proper _c_type_ when not including newlib.


Now I am trying got compile libstdc++ with different options. I would like to have both versions with and without exceptions/rtti enabled.

Henning

At 17:49 09.03.2004, you wrote:
Henning Baldersheim wrote:
I am using ecos and would like to be able to use exceptions and stl/iostreams.

You might try one of the ecos lists on http://sources.redhat.com/ecos, for instance the ecos-discuss list.


1 - define a *-ecos in the configure.in/config.sub files.
2 - Make a gthr-ecos.h in gcc subdirectory and change gcc/config.gcc.

Sounds reasonable.


Can anyone give me some hints so I do not make to many mistakes. Are there any documentation on how to add new targets.

If you ask specific question, we may be able to provide answers. We probably can't provide much help to general questions such as how to add a feature or a target.


Now the tools are compiled with --enable-newlib. Is that necessary. I thought c-lib functionality was provided solely by ecos.

ecos does not use newlib. This may or may not be a bug depending on what --enable-newlib does, and where it got enabled. What specifically is the problem here?
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com




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