Outputs generated by crosstool-ng unusable

This forum is for supported devices using an ARMv7 Texas Instruments (TI) SoC.

Re: Outputs generated by crosstool-ng unusable

Postby zombiepantslol » Sun Mar 11, 2012 12:49 am

Okay, my bad, used a wrong parameter with gcc/distcc. Now I did the same thing again and get the same output like you when I do "file test".

However, I still cannot compile a custom kernel using distcc. When I do so, makepkg extracts everything and executes "make prepare" after which I get the following output:

$this->bbcode_second_pass_quote('', '
') HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
/usr/bin/ld: scripts/kconfig/conf.o: Relocations in generic ELF (EM: 3)
/usr/bin/ld: scripts/kconfig/conf.o: Relocations in generic ELF (EM: 3)
/usr/bin/ld: scripts/kconfig/conf.o: Relocations in generic ELF (EM: 3)
/usr/bin/ld: scripts/kconfig/conf.o: Relocations in generic ELF (EM: 3)
/usr/bin/ld: scripts/kconfig/conf.o: Relocations in generic ELF (EM: 3)
/usr/bin/ld: scripts/kconfig/conf.o: Relocations in generic ELF (EM: 3)
scripts/kconfig/conf.o: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
distcc[2413] ERROR: compile (null) on localhost failed
make[2]: *** [scripts/kconfig/conf] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
==> ERROR: A failure occurred in build().
Aborting...


Any ideas?
zombiepantslol
 
Posts: 9
Joined: Mon Dec 26, 2011 1:51 pm

Re: Outputs generated by crosstool-ng unusable

Postby kleptophobiac » Sun Jun 10, 2012 7:07 am

Did you manage to fix this problem? crosstools-ng built OK, but I can't seem to build a kernel with distcc.

-Sasha
kleptophobiac
 
Posts: 10
Joined: Sun Jun 10, 2012 7:03 am

Re: Outputs generated by crosstool-ng unusable

Postby kleptophobiac » Sun Jun 10, 2012 6:01 pm

problem solved.

First problem was the $PATH read order; I had put the crosstools folder at the end rather than the beginning and distcc was building x86 binaries.

Second problem was that I had only made the bin/ folder world read/runnable. You need to make sure that the whole toolsuite folder and all of its parents are too.

I'm happily compiling kernel pkgbuilds now. Thanks to Leming in IRC for helping through my issues!
kleptophobiac
 
Posts: 10
Joined: Sun Jun 10, 2012 7:03 am

Previous

Return to Texas Instruments (TI)

Who is online

Users browsing this forum: No registered users and 7 guests