Hmm, it looks like I have to match exactly architecture subpart of
target on binutils and gcc.
I started woith binutils and targeteed them for Microchip's PIC32, which
should be around mips32r6.
But gcc wouldn't let me use this, so I chose more general mips.
Now it works better only to fail to find ld. Or so it says.
Strace shows that it might have troubles finding crt* stuff, but will
look into that later.
Man, I wish for a page that explains these things in detail and in
breadth - with sufficiently fresh info...
Thanks for your time...
On 12. 03. 19 23:39, Branko wrote:
BTW:
mips-unknown-elf-gcc -print-prog-name=as
gives me simple "as", no canonical name.
no matter what I do, gcc seem to always use first "as" it can find,
which is system as.
I tried doing "AS=/home/brane2/MC_SDK/bin/mips32r6-unknown-elf-as
mips-unknown-elf-gcc test.c
But it always fails with the statement that as doesn't understand
option -EB...
On 12. 03. 19 23:29, Branko wrote:
On 12. 03. 19 22:23, Jonathan Wakely wrote:
On Tue, 12 Mar 2019 at 22:20, Branko <brane221122@xxxxxxxxx> wrote:
I just did.
I've compiled separate binutils for the target and then also
compiled gcc.
We would be able to help more if you told us how you configured
binutils and GCC.
OK, this is the bit of a script I used to config & make binutils:
*****************************
pushd 000_build && rm -Rf *
../configure --target="mips32r6-unknown-elf"
--prefix=/home/brane2/MC_SDK --disable-nls --enable-shared
--disable-multilib
make -j17 && make install && echo && echo "************ BINUTILS
INSTALLED *********************"
popd
***************************************
and this is the script for gcc (v8.3.0) config and make:
****************************************
pushd 000_build && rm -Rf *
export AS_FOR_TARGET=/home/brane2/MC_SDK/bin/mips32r6-unknown-elf-as
export AR_FOR_TARGET=/home/brane2/MC_SDK/bin/mips32r6-unknown-elf-ar
export LD_FOR_TARGET=/home/brane2/MC_SDK/bin/mips32r6-unknown-elf-ld
export NM_FOR_TARGET=/home/brane2/MC_SDK/bin/mips32r6-unknown-elf-nm
export
OBJCOPY_FOR_TARGET=/home/brane2/MC_SDK/bin/mips32r6-unknown-elf-objcopy
export CC_FOR_TARGET=/home/brane2/MC_SDK/bin/mips-unknown-elf-gcc
export CXX_FOR_TARGET=/home/brane2/MC_SDK/bin/mips-unknown-elf-g++
../configure --target="mips-unknown-elf" --prefix=/home/brane2/MC_SDK
--disable-nls --enable-shared --disable-multilib --disable-threads
--enable-languages=c,c++
make -j17 all-gcc && make install && echo && echo "************ GCC
INSTALLED *********************"
popd
************************************
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 ?
It sounds like GCC didn't find your cross binutils. Did you install
binutils, or just compile it? Did you install it somewhere that is in
your PATH, so GCC can find the executables? Alternatively, did you use
--with-as and --with-ld to tell GCC how to find them?
The simplest solution is to install the cross binutils to the same
path as you use for GCC's --prefix option. If GCC finds a binutils in
the --prefix directory then it will use it automatically.
