RedBoot? (ARM newlib build)

[Toralf Lund]

Bill Gatliff wrote:

> Toralf:
>
>
> Actually, arm-elf newlib assumes ARM's toolchain (esp. the Angel 
> monitor/debugger), which works using SWIs.  The following procedure, 
> which I excerpted from one of my training manuals (and I think it's on 
> my website somewhere), rebuilds newlib without SWIs.  Please pardon 
> the reformatting, it looks much better in PDF.  :^)

Ah. Yes. Now I see. I got confused by the fact that I have 
redboot-crt0.o, redboot.ld etc. Those are from libgloss, though, not 
newlib/libc. I'm now building with the attached patch applied...

It is still not clear to me exactly how the correct startup file is 
found, though. The linker scripts included for ARM have no STARTUP() 
directive. But now that I think about it, I remember that I had to 
comment out the one found in the example files when creating the script 
for my m68k setup (i.e. I don't use one there, either.)

>
> As to your second question, don't port anything you don't need.

Yes. That's probably a good principle. It's not quite clear to me if the 
unwanted parts of RedBoot actually involve extra poriting work, though. 
(It could be that those sections are platform independent, and based on 
certain "core" components that will have to be ported anyway.)

>
>
> Regards,
>
>
> b.g.
>

- Toralf
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cross-gcc-nomonARM.patch
URL: <http://sourceware.org/pipermail/crossgcc/attachments/20031211/bf09838a/attachment.ksh>
-------------- next part --------------
------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com