From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Paul Beskeen <paulb@ecoscentric.com>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: Gnutools: consideration for upgrade to GCC 4.6
Date: Tue, 17 Jan 2012 12:28:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.00.1201171511480.13451@sg-pc.belvok.com> (raw)
In-Reply-To: <4F154F95.30203@ecoscentric.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1981 bytes --]
All
I changed my mind. I withdraw my request. All should know what (which
toolchain) they use. If I do not trust myself, no one denies to patch
GCC to get own built-in define, e.g. __home_cooked__ as a memory stick
to distinguish toolchains :-)
Thanks for your points and time!
Sergei
On Tue, 17 Jan 2012, Paul Beskeen wrote:
> On 17/01/2012 09:57, Bernard Fouché wrote:
> > Le 16/01/2012 22:11, Sergei Gavrikov a écrit :
> >> On Mon, 16 Jan 2012, Sergei Gavrikov wrote:
> >>
> >>> I hope I have convinced you and Stano that I did not suggest to
> >>> "close" eCos sources by __ecos__ checks. More that to propagate
> >>> that built-in definition is only a few lines for GCC patch and if
> >>> that is issue I am ready to withdraw my "I like their built-in"
> >>> :-)
> >> Nobody (me too) said (thought) about:
> >>
> >> http://www.ecoscentric.com/trademark_usage.shtml
> >>
> >> AIANL. So, I actually withdraw my "wish" as [eCos] is registered
> >> trademark and anyone would use our patches and abuse the word.
> >>
> >> Sergei
> >
> > Being able to identify/check the toolchain used seems a very good
> > idea. Why not ask eCosCentric about the legal issue? They already
> > make a toolchain available for public eCos, that can be installed
> > with the installation tool (see
> > http://ecos.sourceware.org/getstart.html) . IMHO it is in the
> > interest of eCos to avoid having its public image altered because of
> > bugs that are related to the toolchain and not eCos itself.
>
> On the trademark front there is no issue with the public eCos release
> using this as required (see 1.1.1/4 section in the above referenced
> URL).
>
> On a personal note, I would however avoid the use of __ecos__ in the
> toolchain for all the reasons that Grant has already pointed out.
> Critically, you don't want to limit users to a specific set of
> toolchains.
>
> Regards, Paul.
> --
> Paul Beskeen, Chairman & Director of Engineering
> http://www.ecoscentric.com/
>
next prev parent reply other threads:[~2012-01-17 12:28 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 17:01 Ilija Kocho
2012-01-13 18:54 ` Bernard Fouché
2012-01-13 19:39 ` Ilija Kocho
2012-01-13 19:09 ` Frank Pagliughi
2012-01-13 19:45 ` Ilija Kocho
2012-01-14 10:22 ` John Dallaway
2012-01-14 16:02 ` Sergei Gavrikov
2012-01-15 17:36 ` Grant Edwards
2012-01-15 18:42 ` Sergei Gavrikov
2012-01-15 21:39 ` Stanislav Meduna
2012-01-23 1:01 ` Jonathan Larmour
2012-01-15 22:21 ` Ilija Kocho
2012-01-23 1:07 ` Jonathan Larmour
2012-01-15 22:21 ` Ilija Kocho
2012-01-16 15:20 ` Grant Edwards
2012-01-16 20:43 ` Sergei Gavrikov
2012-01-16 21:11 ` Sergei Gavrikov
2012-01-17 9:58 ` Bernard Fouché
2012-01-17 10:38 ` Paul Beskeen
2012-01-17 12:28 ` Sergei Gavrikov [this message]
2012-01-23 0:59 ` Jonathan Larmour
2012-01-14 16:25 ` Ilija Kocho
2012-01-23 1:13 ` Jonathan Larmour
2012-01-23 18:40 ` Ilija Kocho
2012-01-23 19:29 ` Jonathan Larmour
2012-01-25 12:30 ` Alex Schuilenburg
2012-01-25 20:59 ` Ilija Kocho
2012-01-26 13:36 ` Alex Schuilenburg
2012-01-26 20:18 ` Ilija Kocho
2012-02-13 22:02 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Ilija Kocho
2012-02-20 16:00 ` Alex Schuilenburg
2012-02-20 20:45 ` Ilija Kocho
2012-03-02 16:36 ` Alex Schuilenburg
2012-03-03 13:32 ` Ilija Kocho
2012-03-04 0:10 ` Alex Schuilenburg
2012-03-04 17:49 ` Sergei Gavrikov
2012-03-04 23:08 ` Alex Schuilenburg
2012-03-04 19:37 ` eCos GNU tools 4.6.2-20120125 ready for testing John Dallaway
2012-03-04 23:47 ` Alex Schuilenburg
2012-03-05 8:00 ` Sergei Gavrikov
2012-03-07 13:51 ` Sergei Gavrikov
2012-03-07 11:58 ` Alex Schuilenburg
2012-03-07 13:01 ` Ilija Kocho
2012-03-07 13:39 ` Sergei Gavrikov
2012-03-07 13:13 ` John Dallaway
2012-03-12 16:43 ` Alex Schuilenburg
2012-03-16 15:05 ` Alex Schuilenburg
2012-03-08 17:28 ` Alex Schuilenburg
2012-03-09 9:39 ` Ilija Kocho
2012-03-09 17:15 ` Alex Schuilenburg
2012-03-10 17:16 ` John Dallaway
2012-03-12 16:12 ` Alex Schuilenburg
2012-03-13 13:31 ` Alex Schuilenburg
2012-03-13 14:16 ` Ilija Kocho
2012-03-13 17:47 ` Sergei Gavrikov
2012-03-15 8:50 ` John Dallaway
2012-03-17 14:50 ` Sergei Gavrikov
2012-03-17 20:58 ` John Dallaway
2012-03-17 16:44 ` Stanislav Meduna
2012-03-18 19:10 ` eCos GNU tools 4.6.3-20120315 [Was Re: eCos GNU tools 4.6.2-20120125 ready for testing] Ilija Kocho
2012-04-04 12:57 ` Lambrecht Jürgen
2012-04-04 13:18 ` Ilija Kocho
2012-05-31 8:42 ` eCos GNU tools 4.6.3-20120315 and link time optimization Bernard Fouché
2012-03-05 8:30 ` eCos GNU tools 4.6.2-20120125 ready for testing Tomas Frydrych
2012-03-05 8:56 ` Tomas Frydrych
2012-03-05 9:50 ` John Dallaway
2012-03-05 9:55 ` Anders Montonen
2012-03-05 14:20 ` John Dallaway
2012-03-05 10:16 ` Ilija Kocho
2012-03-05 12:56 ` Tomas Frydrych
2012-03-03 12:58 ` eCos GNU tools 4.6.2-20120125 ready for testing [Was Re: Gnutools: consideration for upgrade to GCC 4.6] Sergei Gavrikov
2012-01-17 9:37 ` Gnutools: consideration for upgrade to GCC 4.6 Tomas Frydrych
2012-01-17 16:10 ` Stanislav Meduna
2012-01-17 16:25 ` Tomas Frydrych
2012-01-17 16:45 ` Ilija Kocho
2012-01-20 14:42 ` Frank Pagliughi
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1201171511480.13451@sg-pc.belvok.com \
--to=sergei.gavrikov@gmail.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=paulb@ecoscentric.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).