public inbox for
 help / color / mirror / Atom feed
From: John Dallaway <>
To: eCos Maintainers <>
Subject: Re: eCos 3.0 beta 1 remaining issues
Date: Wed, 25 Mar 2009 11:01:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]

eCos maintainers

I think the eCos 3.0 branch is now good for a final release. Thank you
to all those who have helped in resolving the last few Bugzilla issues.
I have appended notes on the action taken. I have also attached a draft
version of the release notes.

If you have any comments or concerns, please raise them by the end of
Thursday 2009-03-25. I will then proceed with generating the final release.

John Dallaway

-- cut here --

>> 1000717    	lwIP TCP/IP drops incoming IP packets on SLIP interface

Patch applied

>> 1000719 	lwip_ppp tests build fails when CYGDBG_LWIP_DEBUG turned on

Proposed change seems too invasive at this late stage - documented in
release notes

 >> 1000693 	flash.c assertion failure
> Andrew, can you confirm whether you are able to address 1000693 for eCos
> 3.0 or whether we should push it out to be fixed later please?

Andrew thinks this should be pushed out

>> 1000688 	RedBoot GPL message

I have checked in Sergei's patch

>> 1000689 	ompat/posix/current/tests/signal1 hangs
>> 1000690 	/home/lunn/eCos/work/install/tests/compat/posix/current/tests/signal3 runs forever

I have backed out the change which caused these issues

>> 1000701 	Error building vectors.S for Thumb on AT91 targets

Fixed by using LDR instructions instead of MOV

>> 1000723 	Building eCos C library for synthetic target fails with gcc-3.2

Added to release notes

>> 1000685 	isoinfra limits.h breaks with gcc 4.3.3/synth

Andrew has checked in his fix

>> 1000716 	Error launching GDB to run eCos tests

No obvious cause - added to release notes

[-- Attachment #2: README-draft-090325.txt --]
[-- Type: text/plain, Size: 5144 bytes --]

[ Pre-release version 2009-03-25 - NOT FOR DISTRIBUTION ]

eCos - the Embedded Configurable Operating System - release 3.0 README

March 2009

Welcome to the eCos 3.0 public release. This README contains a list of known
problems with the eCos 3.0 release. Please check for further issues by
searching the Bugzilla database for product "eCos" version "3.0":

If you discover new bugs with this release please report them using Bugzilla:

System Requirements

This release has been tested against Microsoft Windows 2000, Windows XP,
Windows Vista and multiple x86 Linux distributions. Microsoft Windows 95,
Windows 98 and Windows ME are not supported.

The Linux-hosted eCos development tools require libstdc++ v3
(/usr/lib/ Users of Linux distributions which provide a more
recent libstdc++ may need to install a libstdc++ v3 compatibility package.
Installation of the compatibility package may be achieved as follows:

  Fedora:       yum install compat-libstdc++-33
  openSUSE:     zypper install compat-libstdc++
  Ubuntu:       apt-get install libstdc++5

The Linux-hosted eCos Configuration Tool also requires the GTK+ toolkit
version 2.0 or later.

The Microsoft Windows-hosted eCos development tools require a recent
installation of the Cygwin compatibility layer and associated command-line
tools. The Cygwin setup program (installer) may be downloaded at:

An installation of these tools dating from September 2008 or later is
recommended. In addition to the packages provided within the "Base" category
of the Cygwin installer, the following packages must be installed for correct
operation of the eCos installer, eCos host tools, GNU compilation tools and
eCos build system:

  gcc libmpfr1 libpng12 make patch tcltk sharutils wget

eCos 3.0 Errata

* Compilation of eCos has been tested for those targets which use the
following GNU toolchains:

  arm-eabi arm-elf i386-elf mipsisa32-elf m68k-elf powerpc-eabi sh-elf

Compilation of eCos for targets using other toolchains is untested and may
not work correctly.

* The pre-built arm-eabi toolchain does not support ARM7DI and StrongARM
processors. When building eCos for such targets, developers are advised to
use the older arm-elf toolchain based on GCC 3.2.1.

* Occasional internal compiler errors have been observed when building eCos
and tests with the prebuilt m68k-elf toolchain. Such errors are highly
sensitive to any changes in the source code. In many cases, the compiler
optimisation level may be reduced as a workaround. However, note that
building the kernel file clock.cxx without optimisation when configured with
CYGDBG_USE_ASSERTS will also trigger an internal compiler error. In such
cases, removal of the the compiler flag '-fomit-frame-pointer' may serve as a

* The cxxsupp test fails for target 'linux' (the synthetic target) on certain
recent Linux distributions (eg Fedora 10). This failure arises when libgcc
assumes that glibc has initialised the GS register to reference per-thread

* Compilation of the eCos C library for target 'linux' (the synthetic target)
is known to fail when using certain older versions of GCC (eg GCC 3.2) due to
a duplicate definition of getc().

* Compilation of eCos for targets 'atlas_mips64_5kc' and 'malta_mips64_5kc'
fails due to various errors involving a loss of precision while casting.

* Compilation of eCos for targets 'cma28x' and 'fads' fails due to a

* Compilation of eCos for target 'iq80310' fails due to multiple coding
issues within the platform support files.

* The eCos tests 'pselect' and 'cpuload' may fail erroneously on some eCos
targets (false negative).

* eCos lwIP tests may fail to build when CYGDBG_LWIP_DEBUG is enabled due to
a dependency on snprintf().

* The eCos tests 'except1' and 'kexcept1' may fail on certain processors
where an exception is not raised in response to bad alignment (for example).

* The eCos math library test 'pow' is known to fail on SH4 hardware when
using the prebuilt sh-elf toolchain. The cause is unknown but the problem
does not occur with older toolchains.

* The MPC8xx test 'intr0' fails on many MPC8xx targets since the test is not
generalised for correct operation will all MPC8xx CPUs.

* The PSIM PowerPC simulator treats all data cache instructions as noops.
The behaviour is benign with the exception of the dcbz instruction. It causes
the eCos 'kcache2' test to fail on target 'psim'.

* There are a number of minor issues with the eCos Configuration Tool:

  84946 Configtool build progress bar inoperative
  89778 Configtool platforms list is not sorted
  1000619 Configuration tree does not respond to scroll wheel
  1000716 Error launching GDB to run eCos tests

  reply	other threads:[~2009-03-25 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 11:31 John Dallaway
2009-03-25 11:01 ` John Dallaway [this message]
2009-03-25 12:22   ` Bart Veer
2009-03-25 13:05     ` John Dallaway
2009-03-25 14:37       ` Bart Veer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).