public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Philipp Meier" <pme.neratec@gmx.ch>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] ecos-3.0 current stm32 bug?
Date: Thu, 25 Aug 2011 08:54:00 -0000	[thread overview]
Message-ID: <20110825085423.184250@gmx.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1108242135550.19203@vostro>

Hello Sergei

% $(which arm-eabi-gcc) --version
arm-eabi-gcc (eCosCentrc GNU tools 4.3.2-sw) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.

This is the good version, isn't it?

ECOS_REPOSITORY
I have the problem with ecos-3.0 and with ecos-current version (I have both installed).

Cheers
Philipp

-------- Original-Nachricht --------
> Datum: Wed, 24 Aug 2011 21:54:35 +0300 (EEST)
> Von: Sergei Gavrikov <sergei.gavrikov@gmail.com>
> An: Philipp Meier <pme.neratec@gmx.ch>
> CC: ecos discuss <ecos-discuss@ecos.sourceware.org>
> Betreff: Re: [ECOS] ecos-3.0 current stm32 bug?

> On Wed, 24 Aug 2011, Philipp Meier wrote:
> 
> [snip]
> 
> > I now went a step back and built (under Linux) my "bootloader" and my
> > "application" under Linux using the same ecos sources and
> > configuration files as when I built them under Windows/cygwin.
> > 
> > Therefore - I wanted to see if the problem comes from building under
> > Linux, or from changes in the ecos stm32 parts (or any other ecos
> > parts).
> > 
> > But - I have the same problem as described above; i.e. the problem
> > must be somehow in my Linux toolchain?
> 
> In any case, ask. Maybe you have installed more arm-eabi toolchains,
> i.e. and from another vendor, e.g. from CodeSourcery, etc. Check it,
> please, check your PATH variable
> 
>   % which arm-eabi-gcc
>   % echo $PATH
>   % $(which arm-eabi-gcc) --version
> 
> also
> 
>   % echo $ECOS_REPOSITORY
>   % ecosconfig --version
> 
> also (you told about HG tree)
> 
>   % hg status -R $ECOS_REPOSITORY/..
> 
> It would be nice to be sure that you use the right tools.
> 
> 
> Sergei

-- 
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!		
Jetzt informieren: http://www.gmx.net/de/go/freephone

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2011-08-25  8:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 10:34 Philipp Meier
2011-08-24 11:35 ` Sergei Gavrikov
2011-08-24 14:11   ` Philipp Meier
2011-08-24 14:26     ` Christophe Coutand
2011-08-24 14:58       ` Philipp Meier
2011-08-24 16:44         ` Christophe Coutand
2011-08-25  8:49           ` Philipp Meier
2011-08-25  9:37             ` Christophe Coutand
2011-08-25 10:01               ` Philipp Meier
2011-08-25 10:38             ` Nick Garnett
2011-08-25 11:25               ` Philipp Meier
2011-08-25 12:12                 ` Nick Garnett
2011-08-25 12:13               ` Philipp Meier
2011-08-25 12:31                 ` Nick Garnett
2011-08-25 12:52                   ` Philipp Meier
2011-08-25 13:46                     ` Nick Garnett
2011-08-24 18:54     ` Sergei Gavrikov
2011-08-25  8:54       ` Philipp Meier [this message]
2011-08-25  9:07       ` Philipp Meier

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=20110825085423.184250@gmx.net \
    --to=pme.neratec@gmx.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).