[ACTIVITY] Week 15
== Progress == o GCC 2016.04 source snapshot (4/10) * Reviewed on-going backports * Merged from FSF GCC 5 branch * Packaged and released snaphot o Extended validation (3/10) * Native validation identifies upstream issues - Fixed Glibc warnings raised by GCC 6, committed in Glibc master * Looking at bkk16 job switch to multijob.. o Misc (3/10) * Various meetings == Plan == o Continue on extended validation o GCC ARMv8.1 builtins fix. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
[ACTIVITY] 11 - 15 April 2016
== Progress == LLDB Buildbot Setup [TCWG-241] [1/10] -- Created a new factory for LLDB buildbots. Halted plan to migrate till turning chromebook build green. LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Investigated some failures some of them were fixed by a systemZ support large patch set. -- Failures reduced to 36 locally with some tweaks. Buildbot still showing random results. LLDB ARM Thread Stepping Problem [TCWG-566] [5/10] -- Only happening on Arm linux targets. -- Spent good bit of time debugging this issue. There are multiple problems but root cause is same. -- Initial investigation reveals frame unwinding issues from .plt section. Miscellaneous [1/10] -- Meetings, emails, discussions etc. == Plan == LLDB ARM Thread Stepping Problem [TCWG-566] -- Further debugging and investigation of this issue. -- Figure out a fix for stepping problem on arm linux. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Fri, Apr 15, 2016 at 7:07 PM, Rob Savoye wrote: > static_link Thank Rob for the pointers. Actually i am trying to build cross gcc for ARM aarch 32bit. I moved all `no` flags to `yes`. `../abe.sh --set arch=armv7-a --host arm-linux-gnueabi --target arm-linux-gnueabi --build all`.. Still observing the same issue while building libgcc abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1 error: __fixsfdi undeclared here (not in a function) abe/build/snapshots/gcc.git~linaro-gcc-5-branch/libgcc/libgcc2.c:59:1 error: __aeabi_f2lz defined both normally and as alias attribute if i drop --host flag.. It compiles properly. But the bins are generating for x86_64 instead of arm 32bit with dynamic rather than static as per your pointer. -- Thanks & Regards, M.Srikanth Kumar. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On 04/18/2016 11:43 AM, $rik@nth wrote: > On Fri, Apr 15, 2016 at 7:07 PM, Rob Savoye wrote: > `../abe.sh --set arch=armv7-a --host arm-linux-gnueabi --target > arm-linux-gnueabi --build all`.. Still observing the same issue while > building libgcc > if i drop --host flag.. It compiles properly. But the bins are > generating for x86_64 instead of arm 32bit with dynamic rather than > static as per your pointer. You're trying to cross compile GCC itself to run on an ARM Linux system ? That's not explicitly supported by ABE. You'd need to first build a arm-linux-gnueabi cross compiler, and clone the sysroot from your ARM target. Then it *might* work. ABE primarily builds cross compilers. For ARM hosted GCC, ABE builds natively. - rob - ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Tue, Apr 19, 2016 at 12:08 AM, Rob Savoye wrote: > On 04/18/2016 11:43 AM, $rik@nth wrote: >> On Fri, Apr 15, 2016 at 7:07 PM, Rob Savoye wrote: > >> `../abe.sh --set arch=armv7-a --host arm-linux-gnueabi --target >> arm-linux-gnueabi --build all`.. Still observing the same issue while >> building libgcc > > >> if i drop --host flag.. It compiles properly. But the bins are >> generating for x86_64 instead of arm 32bit with dynamic rather than >> static as per your pointer. > > You're trying to cross compile GCC itself to run on an ARM Linux > system ? That's not explicitly supported by ABE. Yes. I want to compile GCC to run on ARM linux. >You'd need to first build a arm-linux-gnueabi cross compiler, Here i am failing to build arm-linux-gnueabi cross compier for ARM aarch. With the configuraiton it is generating for x86 rather than for ARM. > and clone the sysroot from > your ARM target. Then it *might* work. ABE primarily builds cross > compilers. For ARM hosted GCC, ABE builds natively. I can do the cloning of sysroot once if i can generate cross compiler for ARM. > > - rob - > -- Thanks & Regards, M.Srikanth Kumar. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On Fri, Apr 15, 2016 at 7:07 PM, Rob Savoye wrote: > On 04/15/2016 07:35 AM, $rik@nth wrote: >> On Tue, Apr 5, 2016 at 11:12 AM, Jim Wilson wrote: >>> On Mon, Apr 4, 2016 at 8:18 PM, $rik@nth wrote: There is no way to build static tool chain by using abe tool at all? >>> >>> Maybe modify abe/lib/make.sh to add -static directly to LDFLAGS? > > All the config files in ABE (config/*.conf), have a "static_link" > flag, just set it to "yes". All flags are marked to "yes". But still ABE is generating dynamic bins rather than static. Does it require any other changes as well? binutils.conf:static_link="yes" cloog.conf:static_link="yes" cloog-parma.conf:static_link="yes" cloog-polylib.conf:static_link="yes" cloog-ppl.conf:static_link="yes" eglibc.conf:static_link="yes" ffmpeg.conf:static_link="yes" gcc.conf:static_link="yes" gdb.conf:static_link="yes" gdbserver.conf:static_link="yes" gdk-pixbuf.conf:static_link="yes" glibc.conf:static_link="yes" glib.conf:static_link="yes" gmp.conf:static_link="yes" infrastructure.conf:static_link="yes" isl.conf:static_link="yes" libelf.conf:static_link="yes" llvm.conf:static_link="yes" make.conf:static_link="yes" mpc.conf:static_link="yes" mpfr.conf:static_link="yes" newlib.conf:static_link="yes" ppl.conf:static_link="yes" qemu.conf:static_link="yes" qt-everywhere-opensource-src.conf:static_link="yes" zlib.conf:static_link="yes" > > - rob - > -- Thanks & Regards, M.Srikanth Kumar. ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Cross compilation issue
On 04/18/2016 09:08 PM, $rik@nth wrote: >>> `../abe.sh --set arch=armv7-a --host arm-linux-gnueabi --target >>> arm-linux-gnueabi --build all`.. Still observing the same issue while >>> building libgcc >> You'd need to first build a arm-linux-gnueabi cross compiler, > Here i am failing to build arm-linux-gnueabi cross compier for ARM For the x86_64 hosted cross compiler, just do this: ../abe.sh --target arm-linux-gnueabi --build all It doesn't matter whether this is statically or dynamically linked at all, it's just to compile the next step. It you really want to hack this into existence, I'll note that ABE sets everything up so you can also do manual builds. All the component builds are located in builds/$host/$target. I commonly do an ABE build, then cd into a build directory and tweak configure flags, make flags, etc... The nice thing is that ABE has built all the dependencies, like binutils, etc... so you only have to hack on one part of the build, like GCC. You an always manually add --disable-shared --enable-static if you want. The existing configure options are in the top of config.log. so it's all easy cut & paste. I do this frequently when debugging ABE. If you want to package the binary toolchain after building it, just add --tarbin when running ABE, and it'll make a tarball you can just install. That should also work for the ARM GCC executables, although I've never tested that. - rob - ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
