Cannot compile cross-toolchain for armv7a

[Strange_Attractor]

I am having troubles compiling a cross-toolchain for armv7a-hardfloat-linux-gnueabihf using crossdev, which fails at GCC stage 1 with the following error message:

[Strange_Attractor]

Update: I tried removing LDFLAGS from make.conf. Now crossdev still fails at GCC stage 1 with the error of not being able to compute suffix of object files. config.log however has different contents. The relevant parts:

[Strange_Attractor]

Does noone have any idea? Should I file a bug report?

[frostschutz]

What works for me is armv7a-hardfloat-linux-gnueabi and armv7a-softfloat-linux-gnueabi.

Is there a gnueabihf or is that a typo on your part?

[Strange_Attractor]

I have read here on the forum that armv7a-hardfloat-linux-gnueabihf should be a valid target, so that's why I have used it. However, I have the exact same problem when I try to build a toolchain for armv7a-hardfloat-linux-gnueabi.

[frostschutz]

emerge --info?

I'm on ~amd64 in case that matters...

[Strange_Attractor]

emerge --info output:

[HalfwayToHeaven]

I ran into the same problem as described in the first post, I managed to solve it by doing:

[biergaizi]

Same problem here!

I cannot compile AVR, MIPS, or MinGW toolchains at all. It seems crossdev is no longer able to deal with path of libraries properly! Regardless to my toolchain,

[NeddySeagoon]

Strange_Attractor,

[galanom]

[cwr]

In April 2015 I built AVR and ARM cross-compilers on a _32_bit_ system with
crossdev 20131011. My notes were:

Using gcc-4.7.3-r1, built avr-gcc with:
USE="-openmp" crossdev -t avr -s4 -S --without-headers
and arm-gcc with:
crossdev -v -S -t armv7-none-linux-gnueabi --env
'EXTRA_ECONF="--with-arch=armv7-a
--with-fpu=vfpv3-d16
--with-float-abi=hard
libc_cv_forced_unwind=yes
libc_cv_ctors_header=yes
libc_cv_c_cleanup=yes"'
It isn't clear if the libc_cv settings are still needed.

I don't know how this translates to a 64-bit system.

(The ARM crosscompiler was used to build software for a BeagleBone Black.)

Will

[Strange_Attractor]

[Strange_Attractor]

[firetwister]

Skip this workaround, the patch in the bugreport (next post) works fine

I have the same problem.
I did a system rebuild and my crosstoolchains stopped working. This occured on 2 independent computers, so it looks lika a bug to me. My systems are development systems, so I did some unmasking and installed gcc-5.2.0. I'm not complaining
For me the whole issue is a bit more complicated, because the same linker version is used for 3 Architectures on my system. So just adding the search path won't cut it if both crosstolchains use it.

How to fix this the dirty way:
1. Call your cross assembler

[firetwister]

Looks like binutils-config is broken. There is a patch in the bugreport.
cross-*/binutils with sys-libs/binutils-libs - executables incorrectly linked to host lib{bfd,opcodes}.so rather than target libraries

[proteusx]

[E-Razor]

Same issue here with AVR.

Applied the patch, /usr/bin/binutils-config looks correct (patch applied).

But still the same issue.


Any other hints?

--

EDIT:

rebuilding binutils-libs fixed it

[firetwister]

I recently ran into the same problem again (see 4 posts earlier), but this time the workaraounds was not possible, because there were no other search dirs before the host binutils libs got loaded.
Strangely I was able to compile a powerpc cross toolchain, but not my desired armv7a-hardfloat-linux-gnueabi, so I suspect something being wrong with my system.

Workaround is quite simple, lasts untill the next rebuild of cross-binutils.