Comment 8 for bug 1304267

Thank you very much!
I forgot one option which led multilib link fail.
After I added that option, link works OK.

I still have one question.
I use crosstools-ng latest code to build multilib toolchain, I
modified t-mlibs to add arm mode softfp armv7-a support

the multilib options is "-marm -march=armv7-a -mtune=cortex-a9
-mfloat-abi=softfp -mfpu=vfpv3"
When building process goes to build libgcc stage 2, I always get the
following errors:

libgcc_s.so.1.tmp uses VFP registers, but xxx.o does not

I can't get any clue about this error.
Could you give me some suggestions about this error?

On Wed, Apr 9, 2014 at 1:44 PM, Zhenqiang Chen
<email address hidden> wrote:
> Then what's you link option? It seams you do not add the multilib
> options when linking the object files:
>
> arm-linux-gnueabihf-gcc -marm -march=armv4t -mfloat-abi=soft ...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1304267
>
> Title:
> Linaro arm linux gnueabihf gcc always add Tag_FP_arch: VFPv3-D16 when
> building .S file with -mfloat-abi=soft
>
> Status in Linaro GCC:
> New
>
> Bug description:
> I have a ASM file with extension .S
> After I build this file with option
> "-marm -march=armv4t -mfloat-abi=soft -c xxx.S -o xxx.o"
> I checked xxx.o with command "arm-linux-gnueabihf-readelf -A xxx.o"
>
> And the output is
> Attribute Section: aeabi
> File Attributes
> Tag_CPU_name: "4t"
> Tag_CPU_arch: v4T
> Tag_ARM_ISA_use: Yes
> Tag_THUMB_ISA_use: Thumb-1
> Tag_FP_arch: VFPv3-D16
>
> I noticed tag " Tag_FP_arch: VFPv3-D16", this tag prevents this xxx.o
> from linking with other .o files.
>
> However, when building .c or .cpp files, the generated .o files don't
> have " Tag_FP_arch: VFPv3-D16"
>
> It seems that AS doen't respect option "-mfloat-abi=soft" and always
> add "Tag_FP_arch: VFPv3-D16" to the genrated .o files
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gcc-linaro/+bug/1304267/+subscriptions