I just did.
I've compiled separate binutils for the target and then also compiled gcc.
Result runs fine without parameters. But as soon as I give it to compile
even trivial program, it chokes with the message like:
"as: unrecognised option -EB"
It shows that this gcc always calls system AS/AR/LD, no mater what I do
or how I compile it.
Is there any special trick for this ?
I tired using configure option AS_FOR_TARGET,AS etc.
With no change in end result...
On 12. 03. 19 20:43, Jonathan Wakely wrote:
On Tue, 12 Mar 2019 at 18:33, Branko <brane221122@xxxxxxxxx> wrote:
I'd like to use my system gcc if possible to compile for such simple
micro ( no OS, no infrastructure, need barebone implementation).
I'm running Gentoo on x86_64, with gcc-8.3.0
Then your system compiler can only compile for x86_64 and x86.
So I cobbled up one three line example and within it just main functioin
that does nothing, except returns.
Then I tried "gcc -march=24kc main.c".
But compiler fails with unknown architecture, even though 24ks is listed
under MIPS.
But your system compiler targets x86_64.
A given build of GCC targets a single CPU architecture. Yours targets
x86_64, not MIPS.
It outputs a list of suppported arches, and all of them are just within
x86/x86_64 world. No ARM, not Power, nothing else.
How should this be done ?
I don't think about going crosscompile as the compiler will run on my
host machine, while it's results would run on the micro...
That's the definition of a cross compiler, and is what you need to do.
You'll have to get a MIPS cross-compiler that runs on your host
machine, or build one yourself.
