This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ecos2.0beta
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: Reinhard JESSICH <Reinhard dot JESSICH at frequentis dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Thu, 20 Mar 2003 11:41:30 +0000
- Subject: Re: [ECOS] ecos2.0beta
- References: <se79b3f7.009@mail.frequentis.com>
Reinhard JESSICH wrote:
Hello,
I have seen on the ecos homepage, that the new official compiler is gcc-3.2.1.
I saw that you are using newlib.
As far as I understand it, you need it to compile gcc.
You don't use it in ecos. Ecos provides its own libc.
If I am right with my assumption about newlib, wouldn't it be better to add the missing
headers to ecos and tell gcc to use them during the compilation?
Actually we'd rather not generate toolchains that way. By generating
toolchains with newlib, it's possible to run "make check" on the compiler
with the built-in simulators without requiring eCos ports for all of them.
I use gcc-3.2.2 ( powerpc-eabi, i586-pc-linux-gnu [synth] ) and I got it to compile
without newlib.
Oh that's certainly possible, and indeed should probably work. The 2.95
instructions didn't require newlib either for example.
> I don't use libstdc++, but I moved the needed runtim functions to
> libgcc.
We wouldn't want to use non-standard setups ourselves, but I'm sure there
are people interested in what you've done. Thanks!
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "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