This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG 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 06 Jul 2015 17:39, ANDY KENNEDY wrote: > From: Mike Frysinger > > On 06 Jul 2015 16:00, ANDY KENNEDY wrote: > > > It seems that we are required to use the eabi system calls at boot for > > > this processor. Is that real or have we fallen off into the weeds on > > > this? We are not (by far) mips experts. > > > > if you only need it for the boot loader (e.g. u-boot), then you don't want a > > linux/glibc toolchain. people use something like mips-elf (*) instead and that > > can either use newlib or forego the C library entirely. > > In the end, I'll need both Linux and u-Boot. At the moment, I'd settle > for u-Boot only. I cannot seem to make the eabi stuff work correctly. > I'm missing "qp" from the instruction set -- not that I have a clue > what that means :). I have made a toolchain for Linux that worked after > booting through RedBoot -- but that same toolchain didn't seem to do the > right thing for building u-Boot. Linux (the kernel) can be built using the same bare metal toolchain as the boot loader, but it could probably also be built using a linux/glibc toolchain while also targetting EABI. but i'm not sure what the status is of userland EABI MIPS. you're probably in untested waters there. -mike
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |