4.10 Approaching

[Ralf Corsepius]

On 09/30/2009 07:48 PM, Till Straumann wrote:
> Ralf Corsepius wrote:
>> On 09/30/2009 06:54 PM, Kate Feng wrote:
>>> Ralf Corsepius wrote:
>>>> On 09/30/2009 05:36 PM, Feng, Kate wrote:


>> Are using home-grown toolchains based on the contents of
>> ftp://ftp.rtems.org/pub/rtems/SOURCES/4.10 ?
> E.g., we are here.
>
> IMO, prior to even thinking about cutting 4.10
> the toolchain versions, patches etc. should be defined, frozen and
> published (as source-code, not only binary releases).
The master source of the patches can be found in RTEMS's source tree in 
CVS: contrib/crossrpms/patches

All other places these can be found are "secondary", e.g.
* inside of the SRPMS (for rpm based distros)
* the src.tar.bz2's (for cygwin and mingw32)

ftp://ftp.rtems.org/pub/rtems/SOURCES/4.10 is "yet another place", meant 
to be "legacy/convenience" to those users, who, for one or the other 
reason don't want to use the prebuilt toolchains.

Users, who are using one of the OSes, we support prebuilt toolchains for 
(openSUSE, CentOS/RHEL, Fedora, Mingw32, Cygwin), should feel advised to 
use these - By not using them, you are making your and our lives 
unnecessarily complicated ;)


> Once we have the final tools then we can build + test 4.10 release
> candidates.
Like with previous releases, the toolchains versions are "rolling" and 
will be updated "when necessary" rsp. "inavoidable".

What might confuse users who aren't closely following the workflow, what 
currently is named "rtems4.10" toolchains, is the "unstable/bleeding 
edge" of RTEMS development, which we try to keep as close as possible to 
its components' upstreams' "stable releases"
(GCC, gdb, binutils, newlib), thus is undergoing rapid development.

Ralf