From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,bc1361a952ec75ca X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-09-10 13:25:44 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-out.nuthinbutnews.com!propagator2-austin!propagator!feed2.newsfeeds.com!newsfeeds.com!newsranger.com!www.newsranger.com!not-for-mail Newsgroups: comp.lang.ada From: Simon Clubley References: <9n2jcd$b50$1@nh.pace.co.uk> <9n3h11$9ic1@news.cis.okstate.edu> <9n7vfh$nq6$1@nh.pace.co.uk> <9n8o51$aik1@news.cis.okstate.edu> <9nala6$p3$1@nh.pace.co.uk> <9nhbjd$dcg$1@suaar1aa.prod.compuserve.com> Subject: Re: RTEMS and Ada, Was: Re: Ada OS talk (was: Progress on AdaOS) Message-ID: <1l9n7.2707$%u4.10169@www.newsranger.com> X-Abuse-Info: When contacting newsranger.com regarding abuse please X-Abuse-Info: forward the entire news article including headers or X-Abuse-Info: else we will not be able to process your request X-Complaints-To: abuse@newsranger.com NNTP-Posting-Date: Mon, 10 Sep 2001 16:25:33 EDT Organization: http://www.newsranger.com Date: Mon, 10 Sep 2001 20:25:33 GMT Xref: archiver1.google.com comp.lang.ada:13005 Date: 2001-09-10T20:25:33+00:00 List-Id: On 10 Sep 2001 15:29:45 -0400, in article , Stephen Leake wrote: > >Simon Clubley writes: > >> >> The situation's a bit more complicated than that. :-) >> >> OARcorp _do_ support Ada as a development environment for RTEMS. However, >> some of the BSP's (for example, the i386 BSP) have moved from COFF to ELF. > >Hmm. In my experience, a Board Support Package (BSP) is written in C, >or Ada, or (most likely) Assembler. _not_ object code. > In this case, the RTEMS BSP's are written in C. >So what does it mean that a BSP has "moved from COFF to ELF"? > >Maybe the BSP defines the loader, and it needs to know the object file >format. I guess that would make sense. > Yes, I was not precise enough here. Your description above is closer, although as I have not yet successfully built RTEMS with Ada support and as my background is VMS and not Unix, I am still a little unsure on the fine details. My understanding is that, amongst other things, a specific BSP's build environment is designed differently depending on if COFF or ELF formats are in use. >> The current GCC used for GNAT, 2.8.x, generates COFF format >> binaries. > >This is misleading. GCC, the compiler, does not generate binaries; it >generates Assembler code. The system assembler and linker generate >binaries. If using the Gnu assembler and linker, they come from the >binutils package, not the gcc package. So just because GNAT uses gcc >2.8.1, does not mean RTEMS can't use it with binutils 2.11 (latest on >Gnu site). > >I suppose there may be some upward incompatibilities, but I'd be >surprised. > I do know that when I attempted to do just this (with or without the OARcorp supplied patches to the gcc/gnat/binutils sources), in order to get pre-ELF versions of the i386 BSP working with GNAT, then the build failed in various ways. >> It has been commented on several times in the RTEMS mailing list >> that OARcorp are eagerly awaiting for ACT to deliver a GNAT for GCC >> 3.x. :-) > >They don't have to use only the binary distributions from ACT! I would >consider it part of a 3rd parties job, to repackage things for exactly >this kind of reason. I never implied that they were waiting for a binary distribution. :-) Like the rest of us, I understand they are waiting for ACT to release a source distribution. OARcorp do optionally build some binary environments for easy installation, but generally RTEMS is built from source and a GNAT cross-compiler (or just GCC if you are not interested in using Ada with RTEMS) is also built from source as part of the installation. > >-- >-- Stephe Simon. PS: Once again, I am not associated with OARcorp in any way apart from an interest in RTEMS. -- Simon Clubley, simon_clubley@remove_me.excite.com-Earth.UFP In the task of removing Microsoft from the marketplace, I have discovered a truly remarkable plan, but this signature is too small to contain it.