Jim, Need your expertise here.

I've tried building in a different machine and end up with different error.

Command used `../abe.sh --set cflags="-static" --set
ldflags="-pthread"  --build x86_64-linux-gnu   --host
arm-linux-gnueabi --target arm-linux-gnueabi   --build all`

/home/hydlnxbld84/Srikanth/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/gcc/real.h:79:76:
error: size of array test_real_width is negative
   [sizeof (REAL_VALUE_TYPE) <= REAL_WIDTH * sizeof (HOST_WIDE_INT) ? 1 : -1];
                                                                            ^
make[2]: *** [c/c-lang.o] Error 1
make[2]: *** Waiting for unfinished jobs....


On Fri, Apr 1, 2016 at 7:40 PM, $rik@nth <srikanth0...@gmail.com> wrote:
> Hi Jim,
>
> I've read the Wiki page and start using abe tool to build cross
> compile for ARM on x86 build system. But i am getting below error.
> Also --set arch=arm argument is showing the arch is not found while 
> configuring.
>
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __fixdfdi undeclared here (not in a function)
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __aeabi_d2lz defined both normally and as âaliasâ attribute
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3:
> warning: parameter names (without types) in function declaration
> [enabled by default]
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3:
> warning: parameter names (without types) in function declaration
> [enabled by default]
> make[2]: *** [_fixdfdi.o] Error 1
> make[2]: *** Waiting for unfinished jobs....
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __fixsfdi undeclared here (not in a function)
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __aeabi_f2lz defined both normally and as âaliasâ attribute
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3:
> warning: parameter names (without types) in function declaration
> [enabled by default]
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3:
> warning: parameter names (without types) in function declaration
> [enabled by default]
> make[2]: *** [_fixsfdi.o] Error 1
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __fixunssfdi undeclared here (not in a function)
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __aeabi_f2ulz defined both normally and as âaliasâ attribute
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3:
> warning: parameter names (without types) in function declaration
> [enabled by default]
> make[2]: *** [_fixunssfdi.o] Error 1
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __fixunsdfdi undeclared here (not in a function)
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1:
> error: __aeabi_d2ulz defined both normally and as âaliasâ attribute
> /local2/mnt/tools/Linux-kernel/Linaro-GCC/abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:3:
> warning: parameter names (without types) in function declaration
> [enabled by default]
> make[2]: *** [_fixunsdfdi.o] Error 1
>
> On Thu, Mar 31, 2016 at 4:00 PM, $rik@nth <srikanth0...@gmail.com> wrote:
>> On Thu, Mar 31, 2016 at 12:51 PM, $rik@nth <srikanth0...@gmail.com> wrote:
>>> On Thu, Mar 31, 2016 at 8:59 AM, Jim Wilson <jim.wil...@linaro.org> wrote:
>>>> On Wed, Mar 30, 2016 at 7:37 PM, $rik@nth <srikanth0...@gmail.com> wrote:
>>>>> You mean if i set --host=arm-linux-gnuebi and
>>>>> --target=arm-linux-gunebi should automatically pick cross compilers
>>>>
>>>> Yes, in theory, it should find CC, AS, AR, etc by itself.  Don't
>>>> forget that you need to set all 3 of build, host, and target for this
>>>> to work.
>>>>
>>>>> instead of pointing them? I am just following Linaro website on how to
>>>>> build cross tool chain
>>>>> https://wiki.linaro.org/WorkingGroups/ToolChain/BuildingGNUToolchains
>>>>
>>>> That page only talks about a basic cross build.  it doesn't talk about
>>>> cross building a native.
>>>>
>>>>> Please let me know if there is some more links where i can follow 
>>>>> precisely.
>>>>
>>>> We call it a "canadian cross" when build != host != target.  What you
>>>> are trying to do is very similar to a canadian cross, and works
>>>> basically the same way.  If you do a web search for "build canadian
>>>> cross gcc" then you can find some web pages that talk about this.  In
>>>> general, this isn't well documented, because it is much harder to do a
>>>> canadian cross than a regular cross, and it usually requires learning
>>>> quite a bit about how gcc builds work in order to be able to do it
>>>> successfully.
>>>>
>>>> We have a tool called ABE that we use for builds inside linaro.  There
>>>> is a wiki page for it at
>>>>     https://wiki.linaro.org/ABE
>>>
>>> Thanks you. I will go through this utility for building native toolchain.
>>>
>>>> I know that this has support for a windows canadian cross build, e.g.
>>>> build=x86_64-linux host=i686-w64-mingw3 and then a target or arm or
>>>> aarch64.  I don't know offhand if it can be used for what you are
>>>> trying to do.
>>>>
>>>> Building a native gcc binary is much easier than trying to cross build
>>>> a native.  You should do a native build if you can.
>>>
>>> Though this is very new to me. Definitely i will give it a try as you
>>> mentioned this process is very easy to build native gcc binaries. But
>>> here i want to build static binaries and where i need to pass the
>>> Flags to ABE. There is no argument supports to build static tool
>>> chains.
>> I gone through the script and saw there are env settings [--set
>> {cflags|ldflags|runtestflags|makeflags}=XXX]
>>>
>>>>
>>>> Jim
>>>
>>>
>>>
>>> --
>>> Thanks & Regards,
>>> M.Srikanth Kumar.
>>
>>
>>
>> --
>> Thanks & Regards,
>> M.Srikanth Kumar.
>
>
>
> --
> Thanks & Regards,
> M.Srikanth Kumar.



-- 
Thanks & Regards,
M.Srikanth Kumar.
_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/linaro-toolchain

Reply via email to