[Bug 936463] cross-*-gcc5 seems to lack some required files
http://bugzilla.novell.com/show_bug.cgi?id=936463
http://bugzilla.novell.com/show_bug.cgi?id=936463#c26
--- Comment #26 from Richard Biener
(In reply to Richard Biener from comment #21)
As it works for me with some targets isn't it only a disconnect between the binutils and cross-gcc target triplets? There must be some configure magic to tell GCC not only about the build tools to use but about the tools to use in the installed system. --with-as/--with-ld might work here I guess? I really don't like the extra symlinks.
Or we want to forgo with the idea to have multiple cross toolchains for the "same" target (like armv6hl and armv7hl as they just differ in their set of default target options). Or we stop producing just a single cross-binutils package for them.
I also strongly prefer to have just one compiler for arm. Rationale:
1. cross-armv6hl-gcc and cross-armv7hl-gcc are essentially identical * same set of possible targets * both have "--with-float=hard" 2. everyone else uses an arm-<foo>-gnueabi triplet
Only minor downside is a little bit of convenience, as one builds by default for the instruction set of the RPi1, the other one for everything else.
I'm all for this. Currently we are using armv[67]hl-suse-linux-gnueabi and configurations %if "%{TARGET_ARCH}" == "armv6hl" --with-arch=armv6zk \ --with-tune=arm1176jzf-s \ --with-float=hard \ --with-abi=aapcs-linux \ --with-fpu=vfp \ --disable-sjlj-exceptions \ %endif %if "%{TARGET_ARCH}" == "armv7hl" --with-arch=armv7-a \ --with-tune=cortex-a15 \ --with-float=hard \ --with-abi=aapcs-linux \ --with-fpu=vfpv3-d16 \ --disable-sjlj-exceptions \ %endif do they do differ in some details. If we simply use arm-suse-linux-gnueabi what default would you use? Should I simply use the armv6hl settings for now? Or what GCC would use as default (probably not hard float I guess)? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com