This is the mail archive of the
mailing list for the eCos project.
Re: eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6]
- From: Ilija Kocho <ilijak at siva dot com dot mk>
- To: Alex Schuilenburg <alexs at ecoscentric dot com>
- Cc: eCos developers <ecos-devel at ecos dot sourceware dot org>
- Date: Sat, 03 Mar 2012 14:32:26 +0100
- Subject: Re: eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6]
- References: <4F106345.firstname.lastname@example.org> <4F11574D.email@example.com> <4F11AC54.firstname.lastname@example.org> <4F1CB41C.email@example.com> <4F1DA9A0.firstname.lastname@example.org> <4F1FF5AD.email@example.com> <4F39887A.firstname.lastname@example.org> <4F50F700.email@example.com>
On 02.03.2012 17:36, Alex Schuilenburg wrote:
> Hi Ilija,
> On 2012-02-13 22:02, Ilija Kocho wrote:
>> 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
>> I guess this one is closest to you:
>> And here are the patches:
> Thanks. I have taken a test snapshot of anoncvs on 2012-03-01
> 00:00:00:00 along with the toolchain above and thrown that to our test
> farm. Unfortunately the Embedded Artists LPC2468-32 anoncvs port
> appears to be either incompatible with our RedBoot or is broken in
> anoncvs. All the tests fail to hit a breakpoint set at cyg_test_init,
> or run without any breakpoints. I suspect this port appears to have
> suffered bitrot since the V3 as the board appears to have been run in
> our testfarm for the public eCos 3.0 release in 2009, and the RedBoot on
> the board is dated Apr 25 2008 which goes back to V2.
> I have just switched to using our eCosPro sources and the first couple
> of tests I checked passed, so at least this confirms this is not any
> issue with the toolchain. Using the same set of eCosPro sources with our
> ecospro tools and the anoncvs tools at least will tell us if there is
> any regression. Unfortunately though, if there is a regression we will
> only be able to report the test/s that failed along with the flags and
> configuration used to build the tests. Otherwise somebody is going to
> need to fix the anoncvs port for the Embedded Artists LPC2468-32 board.
Thank you Alex.
I think that the first step is to find out whether it is a problem with
EA LPC2468-32 code or more general. Unfortunately I am not able to test
with this board as we don't have one.
I hope that the testing with STM32 may give us some hint.
I also wander if test with RedBoot from current CVS would help.
>> 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.
> I have added the configuration you sent to our test farm, although
> obviously because the sources are eCosPro, there is no uSTL support
> testing for the Embedded Artists LPC2468-32.
> I'll let you know how we get on with the ST STM3210E-EVAL board testing.
> -- Alex
> Managing Director/CEO eCosCentric Limited
> www.ecoscentric.com Reg in England and Wales, Reg No 4422071