This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu, 2005-11-03 at 15:27 +0100, Valentin Longchamp wrote: > Yeah I know all of this ! But what if I for example compile a program > that is going to run on my bare chip without an OS or using for eCos > librairies with an an arm-linux toolchain ? Then you will need yet another toolchain for ecos. > What are the "real precise" difference ! I already know about linux > syscall and glibc and things like that ! Exactly this, different libcs, i.e. different syscalls, different sets of functions implemented libc, and various tiny differences in detail (different ABIs, different startup scripts, different system features etc.). > I want to know what is going to > happen if I compile a program without OS call with arm-linux ? It depends on what exactly you are doing and how you are doing it. In most non-trivial cases, you won't get far. The clean and (in mid-term) less troublesome solution is to use different toolchains. Ralf ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |