Hinko Kočevar wrote: > > Next problem emerges when using $(CROSS_COMPILE)gcc instead of cris-gcc - > toolchain that buildroot creates is cris-linux-uclibc and does not recognize > -melf switch when linking head.o. Using $(CROSS_COMPILE)gcc fails with > assembler > errors Error: Illegal operands.
Above errors are only seen when creating final linux kernel image.. I've hacked the openWRT rules.mk to define different type of final target - instead of cris-linux-uclibc I used cris-axis-elf and rerun the make procedure. Binutils and gcc get built, but if fails at uClibc. It makes sense. Then I reverted the rules.mk and proceeded with normal installation. Now (using cris-axis-gcc for head.o compilation) linux kernel is compiled with success. Now, how would one integrate build of two different target compilers: - cris-linux-uclibc - cris-axis-elf into the openWRT buildroot? I guess we need only binutils and gcc stages (no libc part). Regards, Hinko -- ČETRTA POT, d.o.o., Kranj Planina 3 4000 Kranj Slovenia, Europe Tel. +386 (0) 4 280 66 03 E-mail: [EMAIL PROTECTED] Http: www.cetrtapot.si _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
