public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Sommerfeld <sommerfeld@mikrom.de>
To: "Eigil Krogh Sørensen" <eisor@tcelectronic.com>
Cc: "ecos-discuss@ecos.sourceware.org" <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Questions about CodeSourcery g++ Lite tool chain and eCos
Date: Thu, 07 Apr 2011 12:58:00 -0000	[thread overview]
Message-ID: <4D9DB4D2.3010808@mikrom.de> (raw)
In-Reply-To: <55E5231BD2EB004EB1E67397C33B3A3E39ECFA6F@ex004tcg>

Hi Eigil,

> Which version of the CodeSourcery tool chain do you use. I have "arm-none-eabi". When I use that chain to compile eCos + app. I have the problem, that e.g. printf doesn't call the eCos function and thus nothing is printed.
> 
> Did you build the libraries youself?
> 

I use arm-none-eabi and I like with: "-Ttarget.ld -nostdlib
-L<path>/ecos_install/lib"

Which arm cpu do you use?

Bye...

> 
> -----Original Message-----
> From: Stefan Sommerfeld [mailto:sommerfeld@mikrom.de] 
> Sent: 5. april 2011 10:22
> To: Eigil Krogh Sørensen
> Cc: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] Questions about CodeSourcery g++ Lite tool chain and eCos
> 
> Hi Eigil,
> 
>>
>> . Is it possible to use CodeSourcery g++ Lite toolchain for eCos? I would like to use that because the compiler is newer, gcc-4.5.1, than the gnutools for ARM, that comes with eCos, gcc-4.3. gcc-4.5. can make code ARM11 and Cortex-R/A.
>>
>> . Can CodeSourcery g++ Lite toolchain be used together with eCos config tool in Windows?
>>
>> . Which version of the CodeSourcery g++ Lite toolchain should be used with eCos?
>>
> 
> I'm using latest CodeSourcery toolchain for eCos (the arm gcc). If you want to
> use cygwin you need make version 3.80, because the latest make doesn't work
> correctly with non-cygwin paths and a correctly set CYGPATH variable. Build
> directly in ecos config tool does not work, but creating a config and running
> make in the *_build dir does.
> 
> I hope this helps you.
> 
> Bye...
> 

-- 
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-04-07 12:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05  7:57 Eigil Krogh Sørensen
2011-04-05  8:22 ` Stefan Sommerfeld
2011-04-05 12:59   ` Eigil Krogh Sørensen
2011-04-07 12:58     ` Stefan Sommerfeld [this message]
2011-04-08 10:57 ` [ECOS] " Tarmo Kuuse
2011-04-08 11:19   ` Tarmo Kuuse
  -- strict thread matches above, loose matches on Subject: below --
2011-04-05  7:53 [ECOS] " Eigil Krogh Sørensen

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=4D9DB4D2.3010808@mikrom.de \
    --to=sommerfeld@mikrom.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=eisor@tcelectronic.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).