- linaro-toolchain - lists.linaro.org

by Will Newton

== Progress == * Committed a couple of gdb patches * Debug malloc to a working state, performance improved * First version of glibc aarch64 ifunc support * Found a couple of bugs in binutils aarch64 ifunc support == Issues == * Missed two days due to illness * Power cut and broadband outage on Wednesday afternoon == Plan == * Respin and submit glibc docs patches * Submit glibc aarch64 ifunc code -- Will Newton Toolchain Working Group, Linaro

12 years, 10 months

1
0
0 0

Is there any description about the toolchain release file naming rule?

by YongQin Liu

Hi, All Under this site http://releases.linaro.org/13.09/components/toolchain/binaries/, there are many files released. but do we have any description on the file naming rules? Sorry for my simple question, I just want to know what the files are used for. which one I should select when I need to use toolchain. Like the files below, I can guess that aarch64 means that it will generate files run on aarch64 platform, but I can not guess what's the difference between linux and none, and not know what's the difference between gnu and elf. So if you have any wiki/link about the the naming rules or description about the file, please share me. crosstool-ng-linaro-1.13.1-4.8-2013.09-01.tar.bz2 crosstool-ng-linaro-1.13.1-4.8-2013.09.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_linux.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_linux.tar.xz gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_runtime.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_src.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_win32.zip gcc-linaro-aarch64-linux-gnu-4.8-2013.09-01_win32.zip.xz gcc-linaro-aarch64-linux-gnu-4.8-2013.09-20130912_win32.exe gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09_linux.tar.xz gcc-linaro-aarch64-linux-gnu-4.8-2013.09_runtime.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09_src.tar.bz2 gcc-linaro-aarch64-linux-gnu-4.8-2013.09_win32.zip gcc-linaro-aarch64-linux-gnu-4.8-2013.09_win32.zip.xz gcc-linaro-aarch64-none-elf-4.8-2013.09-01_linux.tar.bz2 gcc-linaro-aarch64-none-elf-4.8-2013.09-01_linux.tar.xz gcc-linaro-aarch64-none-elf-4.8-2013.09-01_win32.zip gcc-linaro-aarch64-none-elf-4.8-2013.09-01_win32.zip.xz gcc-linaro-aarch64-none-elf-4.8-2013.09_linux.tar.bz2 gcc-linaro-aarch64-none-elf-4.8-2013.09_linux.tar.xz gcc-linaro-aarch64-none-elf-4.8-2013.09_win32.zip gcc-linaro-aarch64-none-elf-4.8-2013.09_win32.zip.xz gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_linux.tar.bz2 gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_linux.tar.xz gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_runtime.tar.bz2 gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_win32.zip gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09-01_win32.zip.xz gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_linux.tar.bz2 gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_linux.tar.xz gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_runtime.tar.bz2 gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_src.tar.bz2 gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_win32.zip gcc-linaro-aarch64_be-linux-gnu-4.8-2013.09_win32.zip.xz gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_linux.tar.bz2 gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_linux.tar.xz gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_win32.zip gcc-linaro-aarch64_be-none-elf-4.8-2013.09-01_win32.zip.xz gcc-linaro-aarch64_be-none-elf-4.8-2013.09_linux.tar.bz2 gcc-linaro-aarch64_be-none-elf-4.8-2013.09_linux.tar.xz gcc-linaro-aarch64_be-none-elf-4.8-2013.09_win32.zip gcc-linaro-aarch64_be-none-elf-4.8-2013.09_win32.zip.xz gcc-linaro-arm-linux-gnueabihf-4.8-2013.09-20130912_win32.exe gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.bz2 gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_linux.tar.xz gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_runtime.tar.bz2 gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_src.tar.bz2 gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_win32.zip gcc-linaro-arm-linux-gnueabihf-4.8-2013.09_win32.zip.xz gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_linux.tar.bz2 gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_linux.tar.xz gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_runtime.tar.bz2 gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_win32.zip gcc-linaro-armeb-linux-gnueabihf-4.8-2013.09_win32.zip.xz -- Thanks, Yongqin Liu --------------------------------------------------------------- #mailing list linaro-android(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/mailman/listinfo/linaro-android linaro-validation(a)lists.linaro.org <linaro-dev(a)lists.linaro.org> http://lists.linaro.org/pipermail/linaro-validation

12 years, 10 months

5
5
0 0

CortexM toolchain recommendations

by Trevor Woerner

Hi toolchain gurus, I am about to start some projects working with CortexMx devices and am wondering if anyone has an opinion on which toolchain(s) I should use/investigate? Being a fan of Linaro, my first instinct would be to use cbuild2 to build an arm-none-eabi- toolchain from a 4.8.x tree. But looking around I can't help notice https://launchpad.net/gcc-arm-embedded. Does anyone know if gcc-arm-embedded has things the Linaro toolchain doesn't wrt Cortex M0, M3, and M4 device/instruction support? Best regards, Trevor

12 years, 10 months

3
5
0 0

Fwd: [Bug target/59216] [ARM] negdi*extendsidi regression

by Christophe Lyon

-------- Original Message -------- Subject: [Bug target/59216] [ARM] negdi*extendsidi regression Date: Wed, 20 Nov 2013 18:06:14 +0100 From: christophe.lyon at st dot com <gcc-bugzilla(a)gcc.gnu.org> To: Christophe LYON <christophe.lyon(a)st.com> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59216 --- Comment #2 from christophe.lyon at st dot com --- Basically, the working code does: asrs r3, r2, #31 negs r2, r2 sbc.w r3, r3, r3, lsl #1 while the failing one does: negs r2, r2 asrs r3, r2, #31 -- You are receiving this mail because: You reported the bug.

12 years, 10 months

1
0
0 0

Testing Android on LAVA

by Renato Golin

Hi LAVA folks, I don't know if you guys know, but Android is moving to LLVM for the next release or so. As such, we'll need to do a lot of testing between now and next release to make sure each component can be compiled (and runs correctly) with LLVM on an incremental basis. We're trying to come up with a way for remotely testing the Linux kernel booting on ARM devices, more specifically an Android stack, and I'm finding it hard to do that with my home equipment. Doing that in LAVA would be ideal, and I know the Android team does it already, but our constraints could be a little different. Basically, there are two fronts: 1. Building Android components with LLVM, using a GCC-compiled kernel booting on an ARM board, in LAVA. This is something we should work internally on how to do it, and it'll be between Android, LAVA and Toolchain groups. 2. Building the Linux kernel with LLVM, and using a GCC-compiled image (like stock CyanogenMod) to test the kernel. We don't have such a kernel (many patches), but the LLVMLinux guys do, and that's where they come in. On the second case, the topic of this email, we'd have to liaise with them to fire jobs at LAVA from their own infrastructure (originally, manually only), and that might need some thinking. But ultimatelly, we want to have those jobs running on LAVA, so that later on we'd be able to have a third layer: Linux+Android built with LLVM with the same system level tests. Since the LLVMLinux guys don't have access to much ARM hardware, and since it's easier for us to scale (or to re-define) hardware requirements, having them running on LAVA makes even more sense. Is this something we can do? Is this being done already? Is this just a question of legal/corporate decision, or is there any technical issues we have to look into? Android folks, It might make more sense if you guys just grab their kernel and build the Android system based on that internally, so that we don't need external access to job submissions in LAVA, but that would mean work from you guys to patch it up, and that might not be in the roadmap for the next months. Is that a feasible route? cheers, --renato

12 years, 10 months

1
0
0 0

[ANNOUNCE] Linaro GCC 4.7 and 4.8 2013.11 released

by Christophe Lyon

The Linaro Toolchain Working Group is pleased to announce the release of both Linaro GCC 4.8 and Linaro GCC 4.7. Linaro GCC 4.7 2013.11 is the twentieth release in the 4.7 series. Based off the latest GCC 4.7.4+svn204656 release, this is the seventh release after entering maintenance. Interesting changes include: * Updates to GCC 4.7.4+svn204656 Linaro GCC 4.8 2013.11 is the eighth release in the 4.8 series. Based off the latest GCC 4.8.2+svn204657 release, it includes performance improvements and bug fixes. Interesting changes include: * Updates to GCC 4.8.2+svn204657 * Fixes for bugs LP #1243656, #1243022 * Backport fix for PR/58423 * AArch64: added support for tiny model GOT access. * Improved Aarch32 A-profile multilibs support (--with-multilib-list option) The source tarballs are available from: http://releases.linaro.org/13.11/components/toolchain/gcc-linaro/4.7 http://releases.linaro.org/13.11/components/toolchain/gcc-linaro/4.8 Downloads are available from the Linaro GCC page on Launchpad: http://www.linaro.org/downloads/ More information on the features and issues are available from the release pages: https://launchpad.net/gcc-linaro/4.7/4.7-2013.11 https://launchpad.net/gcc-linaro/4.8/4.8-2013.11 Mailing list: http://lists.linaro.org/mailman/listinfo/linaro-toolchain Bugs: https://bugs.launchpad.net/gcc-linaro/ Questions? https://ask.linaro.org/ Interested in commercial support? Inquire at support(a)linaro.org

12 years, 10 months

1
0
0 0

[Activity] Nov 10-16

by Rob Savoye

= Progress == * Created Cards for the infrastructure Team TODO list. * Finished Cbuildv2 support for building GDB binary tarballs. * Got Arch linux up on Odroid XU board again, seems stable, did a build and test run. * Experimented with lava-tool. * Tried to get GCC trunk building native on aarch64 for libsanitizer patch testing. * Upgraded gmp to 5.1.3 in infrastructure/ to work around a configure bug triggered by crouton native builds on a chromebook. * Setup chromebook slaves in new toolchain build farm. * Started adding support to Cbuildv2 to handle git URLs with a user name, ie.. git(a)staging.git.linaro.org to work around git repo problem. == Plan == * Finish support for user names in URLs. * Continue on remote testing support. * Keep trying gcc trunk on aarch64 native. * Fix git repo. == Issues == * GCC git repo hasn't been auto updating the svn branch of linaro-4.8-branch. It used to work... updating manually is now broken as well. * Somehow qemu snapshots tarballs are overwriting the toolchain directories on snapshots.linaro.org. * I don't think lava-tool is going to be useable for toolchain testing, as it only queues up an executable test case to be run later, whereas GCC expects the test to get run right away.

12 years, 10 months

1
0
0 0

[ACTIVITY] 12-15 November 2013

by Christophe Lyon

One day off == Progress == * Prepared 4.7 and 4.8 2013.11 releases. Some delay because of board crashes and disk full issues. * Aarch64: committed 'frame grows downward' patch. This removes a dependency for libsanitizer and libssp. * libsanitizer on Aarch64: blocked by GCC trunk not bootstrapping currently on Aarch64 HW (reported by Rob) * Looked at cross-build failures of trunk after new -fisolate-erroneous-paths. Ramana pointed me to Marcus' glibc patch, and I could switch my builds from eglibc to glibc. * cross-validations: updated list of configurations built&tested after discussion with Richard during Connect. == Next == * Announce 4.7 and 4.8 2013.11 releases * Continue investigating 'extended neg' fix (aka tar regression) * Look for patches to fix AArch64 bootstrap, so that we can test libsanitizer

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 46

by Yvan Roux

One day off. == Issues == * Various cbuild issues: - disk full, boards down and benchmarks launched on different boards == Progress == * LRA on AArch32: - Proposed a ARM backend fix for the Fortran issue http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01997.html - Performance analysis ongoing * Merge reviews and backports. == Next == * Continue on LRA

12 years, 10 months

1
0
0 0

[ACTIVITY] 11 - 15 November 2013

by Omair Javaid

== Progress == * Wrote ARM and Thumb stub handlers for simd, vfp and coprocessor instruction recording. * Read documentation on VFP and Neon register set to figure out a register recording method. * Follow up on upstream patches. * Investigating a un-handled instruction test suite failure in arm process record. * 9th/10th Muharram Public holiday on Thursday and Friday. == Plan == * Fix failures in arm process record due to un-handled instruction. * Get started on writing handlers for coproc, vfp and simd instructions.

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 46

by Zhenqiang Chen

== Issues == * None. == Progress == * One day (Nov. 15) off. * Misc update for Linaro crosstool-ng - Use newlib-linaro-2.0.0-2013.11-1. - Update fortran support related scripts and configs according to Matt's comments. * Propose to support S2_<op1>_<Cn>_<Cm>_<op2> system register in AARCH64 GAS. - Yufeng followed-up it and added full TRACE registers support. * Investigate heuristic to tune ifcombine (TCWG-313) - Got some new fails in regression tests since some optimizations can not get the expected result. - Collect Spec2k INT result. Overall there is no changes. But there are -2 - 1% changes for several cases. - PGO tests are ongoing. == Plans == * Continue on CCMP. * Continue on ifcombine tuning.

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 46

by Renato Golin

== Progress == * Preparing presentation on auto-vec for LLVM - For Cambridge LLVM Day next Monday - If accepted, also for FOSDEM 14 * Tracing strided access changes needed in auto-vec (PR17677) - Reading the paper, preparing a reference implementation - Discussing details and preparing the LLVM code to introduce it - After a few attempts, it's clear that the code is not yet ready to cope with the changes - I'll have to work on the surrounding code to re-factor it for more robust integration - As well as triming some other edges (like pragmas) to help implement it * Planning Android builds - Trying to get a reference platform (most likely the new Arndale) - LLVMLinux folks will help streamlining a kernel package for it * Connect reservations, booking flight, etc. - All done! == Plan == * Monday at Cambridge LLVM Day at CUCL * 3.4 Release testing * Looking at vectorization pragmas and general structure of the memory dependency checks

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 46

by Will Newton

== Progress == * Fix ld testsuite on mainlne * More malloc debugging and refactoring * glibc patch review * Investigate gdb hardware breakpoint issues == Issues == * Didn't get much done on Friday due to sick baby == Plan == * malloc * Follow up glibc docs patches * Further investigate gdb hardware breakpoint issue -- Will Newton Toolchain Working Group, Linaro

12 years, 10 months

1
0
0 0

[ACTIVITY] November 6-8 2013

by Christophe Lyon

Short week: 2 days off after Connect. == Progress == * LP 1243656: reverted commit which causes a regression in GNU tar's tests. * Committed Kugan and Zhenqiang's backports to our branch * Status on backports: ILP32 support missing from binutils is blocking quite a few GCC backports (because of dependencies between commits) * Some problems building trunk since Nov 5th (failures in eglibc) == Next == * Make 2013.11 releases * Continue working on GNU tar problem: find a proper fix. * Commit 'aarch64 frame grows downward' patch if Richard approves it. * Check status of aarch64 lib sanitizer branch if Rob manages to have it build & execute tests * Check Neon intrinsics testsuite status with Rob

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 45

by Yvan Roux

2 post-connect days off. == Issues == * None. == Progress == * LRA on AArch32: - Analyzed testsuite results with last upstream LRA patches. - One remaining regression observed on Fortran. Reported it upstream. - Submitted a fix for the Thumb bootstrap issue http://gcc.gnu.org/ml/gcc-patches/2013-11/msg00776.html - Launched benchmarks for performance analysis * Merge reviews. * Misc: - Internal post-connect feedback meeting. == Next == * LRA : - Look at Steven Bosscher fix http://gcc.gnu.org/ml/gcc-patches/2013-11/msg01029.html - Performance analysis * Backports

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 45 - Nov 4 - Nov 8

by Ryan Arnold

== Progress == * Monday off for recovery from Connect. * Created git_revisions branch for refactoring * Added verified and correct --help and --usage text. * Error check for spurios '=' after --<switch> * Add toplevel test.sh for testing cbuild2.sh commands * Fix get_URL and checkout to support git revisions. * Improve dryrun to prevent grepping missing files. * Added glibc support to cbuild2. * Cleaned up merged cbuildv2 remote development branches * Started cbuild2 bisect. == Plan == * Merge glibc support upstream == Issues == * None

12 years, 10 months

1
0
0 0

[ACTIVITY] 4 - 8 November 2013

by Omair Javaid

== Progress == * Monday and Tuesday off for Jetlag recovery. * Arm process record: - Updated Patches for all fixes and features. - Performed testing in arm native and remote configuration. - Performed regression testing on arm and x86. - Submitted all new patches after updates. * Started gdb.reverse test suite failure investigation and open new Jira issues accordingly. * Started work co-processor instructions decoding for arm process record. == Plan == * Continue work on co-processor instruction decoding for arm process record. * Respond to upstream suggestions on patches sent previously.

12 years, 10 months

1
0
0 0

[ACTIVITY] Week 45

by Zhenqiang Chen

== Issues == * Binaries build FAIL in cbuild, but OK in local build. == Progress == * Misc update for Linaro crosstool-ng - Update newlib to 2013.11. - Modify scripts to meet the check of A-profile multilib support. - Add fortran/libfortran support for bare metal build. - Fix multi-lib conflict issue in local patch - A refer A-profile bare metal build is shared at http://cbuild.validation.linaro.org/snapshots/gcc-linaro-arm-none-eabi-4.8-… * Update conditional compare patch according to comments. * Investigate heuristic to tune ifcombine (TCWG-313). == Plan == * Fix the binaries build FAIL issues. * Continue on CCMP. * Continue on ifcombine tuning. == Planed leaves == * Nov. 15 - 16: Team event and HelloGCC in Beijing.

12 years, 10 months

1
0
0 0

[ACTIVITY] 4 November - 8 November 2013

by Kugan

== Progress == - Looked into Cbuild2 and current benchmarking scripts - Talked to Rob to understand the requirements and plan for next 2 weeks - Backported gcc testcase fix that causes regression in Linaro 4.8 for armv5te. == Plan == - Taking leave next week. - Start with benchmarking scripts after that

12 years, 11 months

1
0
0 0

[ACTIVITY] 4 November - 8 November 2013

by Venkataramanan Kumar

Worked from AMD Austin. == Progress == * TLS based libssp support. Solved segmentation faults in clone and fork tests regressing from the patch I wrote. Ran glibc tests. Two tests still fail, tst-cancel-17.c and tst-memqueue8.c. They both use pthread_cancel and with my patch they time out. Debugging it to find the cause. Informed Maintainer about my status and got some advice to debug. == Plan == * Taking vacation next week. * But will continue send out gcc patch for libssp. * reinstall ubuntu on my laptop

12 years, 11 months

1
0
0 0

[Activity] Nov 2-10

by Rob Savoye

== Progress == * Enabled building GDB in all Cbuildv2 builds for --build all. * Added support for Cbuildv2 to to build GDB source tarball. * Got Canadian Crosses building via Cbuildv2, although I have to apply a one line patch, which I was trying to avoid. * Enabled Canadian Cross builds via Jenkins. * Source and binary snapshots builds via Jenkins now getting copied to snapshots.linaro.org. * Got started migrating Christophe's neon intrinsic test cases to GCC testsuite. * Added DejaGnu 'linaro' branch to Cbuildv2 infrastructure so the new baseboard files are available for Jenkins builds. * Applied Christophe's libsanitizer patch on aarch64 APM board and tried to get GCC to compile. Unsuccessful so far. * Installed crouton 'saucy' on new HP Chromebook 11. * Installed Fedora 19 on Samsung Chromebook. * Started adding support to Cbuildv2 for building LLVM and Clang and other components. I wish they all used autotools. :-) * Got Gerrit working for GCC and Cbuildv2. The LAVA team has been very helpful, but the setup docs miss way too many critical details. == Plan == * Figure out how to gpg sign the tarballs cbuildv2 is producing in a secure manner. * Finish adding support for building GDB binary tarballs. * More work on neon intrinsics test cases. * Work with new team member Mike to help him get up to speed on all things Linaro. * Try to get GCC trunk to build on aarch64. * Off to the "Hacker's Conference" out here in Santa Cruz, back home late Monday night. == Issues == * Eglibc defines caddr_t as a typedef, where auto-host for a Canadian Cross defines caddr_t, so stage2 fails to build. * Sucked up all the disk space in the toolchain_cloud instance, so all Jenkins builds are not working. * We'd like to rename Cbuildv2 to something else, suggestions welcome. :-)

12 years, 11 months

2
2
0 0

[ACTIVITY] Week 45

by Renato Golin

== Progress == * LLVM Dev. Meeting 2013 * Meetings with Google, Qualcomm and ARM about Android and LLVM * We're creating a task force to move Android to be compiled with Clang by default, kernel, libraries, userland, native apps, Renderscript. * Agreed on some actions for public benchmarking - Hal will move tests to benchmarks by hand - Linaro will create bots on that sub-set == Plan == * Recuperate * Work on the stride vectorizer * Create benchmark bots * Start a TableGen doc seed, so experts can chime in * Prepare something for the CUCL LLVM Day on the 18th

12 years, 11 months

1
0
0 0

[ACTIVITY] Week 45

by Will Newton

== Progress == * Monday recovering from Connect travel * Release Linaro newlib 2.0.0 2013.11 * Committed a number of gdb patches to fix bugzilla issues * Submitted patches for glibc memory manual improvements * Read a couple more papers on malloc == Issues == * None == Plan == * Finish off glibc memory manual and aligned_alloc patches * malloc -- Will Newton Toolchain Working Group, Linaro

12 years, 11 months

1
0
0 0

[ANNOUNCE] Linaro newlib 2.0.0 2013.11 released

by Will Newton

### About Linaro newlib Linaro newlib is a release of the newlib C library with bug fixes and enhancements for ARM platforms. newlib is a small footprint C library designed for embedded systems. ### Linaro newlib 2.0.0 2013.11 The Linaro Toolchain Working Group is pleased to announce the 2013.11 release of Linaro newlib 2.0.0, the second release in the 2.0.0 series. This release is based on the latest upstream newlib trunk, but with additional features and bug fixes. #### Additional Features * Resync with upstream newlib trunk * Improved support for Cortex-A and AArch64 baremetal systems #### Bug Fixes * None ### Source #### Release Tarball * https://releases.linaro.org/13.11/components/toolchain/newlib-linaro #### Development Tree * git://git.linaro.org/toolchain/newlib.git This release was built from the `linaro_newlib-2_0_0-2013_11_release` tag. ### Feedback and Support Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development. * Linaro Toolchain Development [mailing list](http://lists.linaro.org/mailman/listinfo/linaro-toolchain) * Linaro Toolchain IRC channel on irc.freenode.net at `#linaro-tcwg` * Questions? [ask Linaro](http://ask.linaro.org/). * Interested in commercial support? inquire at [Linaro support](mailto:support@linaro.org) -- Will Newton Toolchain Working Group, Linaro

12 years, 11 months

1
0
0 0

[ANNOUNCE] Linaro Toolchain Binaries 2011.10 released

by Bernhard Rosenkränzer

The Linaro Toolchain and Builds and Baselines Working Groups are pleased to announce the 2013.10 release of the Linaro Toolchain Binaries, a pre-built version of Linaro GCC and Linaro GDB that runs on generic Linux or Windows and targets the glibc Linaro Evaluation Build. Uses include: * Cross compiling ARM applications from your laptop * Remote debugging * Build the Linux kernel for your board What's included: * Linaro GCC 4.8 2013.10 * Linaro GDB 7.6.1 2013.10 * A statically linked gdbserver * A system root * Manuals under share/doc/ The system root contains the basic header files and libraries to link your programs against. Interesting changes include: * The sample configurations no longer require the LSB tools * The build now works behind a HTTP proxy The Linux version is supported on Ubuntu 10.04.3 and 12.04, Debian 6.0.2, Fedora 16, openSUSE 12.1, Red Hat Enterprise Linux Workstation 5.7 and later, and should run on any Linux Standard Base 3.0 compatible distribution. Please see the README about running on x86_64 hosts. The Windows version is supported on Windows XP Pro SP3, Windows Vista Business SP2, and Windows 7 Pro SP1. The binaries and build scripts are available from: https://releases.linaro.org/13.10/components/toolchain/binaries/ Need help? Ask a question on https://ask.linaro.org/ Already on Launchpad? Submit a bug at https://bugs.launchpad.net/linaro-toolchain-binaries On IRC? See us on #linaro on Freenode. Other ways that you can contact us or get involved are listed at https://wiki.linaro.org/GettingInvolved.

12 years, 11 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linaro-toolchain