Hi Alex eCos GNU tools 4.6.2-20120125 (arm_eabi) binaries are ready for testing. John has placed them on FTP and by now most of the mirrors should have updated.
I guess this one is closest to you: http://www.mirrorservice.org/sites/sourceware.org/pub/ecos/gnutools/i386linux/test/ecos-gnutools-arm-eabi-20120125.i386linux.tar.bz2 And here are the patches: http://www.mirrorservice.org/sites/sourceware.org/pub/ecos/gnutools/src/test/ecos-gnutools-20120125-patches.tar.bz2 The specific feature of public eCos is that it uses uSTL rather than stdlibc++. Would it be possible for you to add ustl with fileio tests? Should I be of any help please contact me. Cheers Ilija On 25.01.2012 13:29, Alex Schuilenburg wrote: > Hi Ilija > > eCosCentric are happy to make its eCos test farm available to you for > automated testing of the new toolchains. > > Having gone through our list of ARM and Cortex hardware in our test farm > and the hardware supported in the public eCos repository (i.e. the > physical hardware we have and what is supported in the public eCos > repository), we propose running tests for the Embedded Artists > LPC2468-32 (to test ARM7 and thumb mode, as well as the network stacks > with the newer toolchain since this board has ethernet support) and the > ST STM3210E-EVAL evaluation board (to test Cortex-M3). > > The tests will take around 2 weeks to run after which I will post the > results for you to examine. The results will be accessible through a > web interface in three forms: > > 1. eCos build results > eCos and its tests will be built in a number of different eCos > configurations utilising a number of different compiler options. > Each configuration is known as a perm (short for permutation). A > build is a tuple consisting of target+source+toolchain+perm. The > results of each build consist of the shell script used to configure > and build eCos and the tests (so you can rebuild yourself), the eCos > ecm export (so you can import the configuration without having to > run the shell script), as well as the full compilation and link > output of the build. > 2. eCos test results > Each test built against a tuple is executed on real hardware with > the test result logged. If a test fails, the full output is > preserved and made available along with the test binary, although > the full output of special tests such as tm_basic are also always > made available. > 3. eCos test result summary > The number of passes and number of each type of failure for each > build is presented in table form to provide an overview of the test > results for the build. > > All we need from you is a Linux hosted arm-eabi toolchain in tarball > form and the eCos sources, also in tarball form, although we can use > http://hg-pub.ecoscentric.com/ecos as the source base if you prefer. > > If you would like to make use of the test farm and agree with the > selection of targets (or can propose alternatives), please let me know > and provide me with the url where the toolchain can be downloaded from > (and optionally the sources). I'll post the results as soon as the > tests are completed. > > Cheers > > -- Alex Schuilenburg > > Managing Director/CEO eCosCentric Limited > www.ecoscentric.com Reg in England and Wales, Reg No 4422071 > > >
