22.8.2016, 17:41, Peter Münster kirjoitti:
On Mon, Aug 22 2016, Jonathan Wakely wrote:
See https://gcc.gnu.org/wiki/FAQ#configure_suffix
Here are the messages found in config.log:
--8<---------------cut here---------------start------------->8---
configure:3464: /home/peter/tmp/no-backup/output/./gcc/xgcc -B/home/peter/tmp/no-backup/output/./gcc/ -B/opt/gcc-mipsel/mipsel-elf/bin/ -B/opt/gcc-mipsel/mipsel-elf/lib/ -isystem /opt/gcc-mipsel/mipsel-elf/include -isystem /opt/gcc-mipsel/mipsel-elf/sys-include -o conftest -g -O2 conftest.c >&5
/home/peter/tmp/no-backup/output/./gcc/as: line 106: exec: -E: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
--8<---------------cut here---------------end--------------->8---
Google suggests installing a cross assembler
(https://gcc.gnu.org/ml/gcc-help/2011-01/msg00266.html). Is this right?
Thanks for your efforts. Kind regards,
Are you this same "Peter" who targets to OpenWRT?
Then maybe the discussion here helps :
https://forum.openwrt.org/viewtopic.php?id=22968
Generally asking whether a crosstoolchain needs cross tools is rather
weird in this stage - one should
earlier be quite well be educated about crosstoolchains, what they are,
and about the target itself, where the
required components : GNU binutils and GCC sources plus the standard
target C library can be found
and downloaded :( Teaching these things to people has been really hard
always because the net is filled
with all kind of "everything from absolute scratch" propaganda stating
that "only sources are allowed"
when the question is about crosstoolchains. Meanwhile the native GCC
builders seem to always understand
that producing the (native) target's standard C library and replacing it
with the self-made one would lead
to a big catasthrope... After all a crosstoolchain is a reincarnation
of the native toolchain for the target on
some other host in most of the cases.
