This is the mail archive of the ecos-devel@sourceware.org mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Gnutools: consideration for upgrade to GCC 4.6

From: Grant Edwards <grant dot b dot edwards at gmail dot com>
To: ecos-devel at sources dot redhat dot com
Date: Sun, 15 Jan 2012 17:36:02 +0000 (UTC)
Subject: Re: Gnutools: consideration for upgrade to GCC 4.6
References: <4F106345.4080902@siva.com.mk> <4F11574D.9070002@dallaway.org.uk> <alpine.DEB.2.00.1201141854480.2289@vostro>

On 2012-01-14, Sergei Gavrikov <sergei.gavrikov@gmail.com> wrote:

> By the way I like their built-in __rtems__ definition for own GCC builds
> and I guess in the end we would propagate __ecos__ for own ones on the
> occasion of renewal.

Why?

Are the eCos sources going to start requiring use of specific
toolchain binaries?

I've been using eCos for a long time, and have always used my own
toolchains.  I'd be pretty unhappy if that was no longer possible.

-- 
Grant

Follow-Ups:
- Re: Gnutools: consideration for upgrade to GCC 4.6
  - From: Sergei Gavrikov

References:
- Gnutools: consideration for upgrade to GCC 4.6
  - From: Ilija Kocho
- Re: Gnutools: consideration for upgrade to GCC 4.6
  - From: John Dallaway
- Re: Gnutools: consideration for upgrade to GCC 4.6
  - From: Sergei Gavrikov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]