public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Biessener <christopherpb@voomtech.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: migration from win2k to win7
Date: Wed, 13 Mar 2013 21:32:00 -0000	[thread overview]
Message-ID: <5140F07F.1080704@voomtech.com> (raw)
In-Reply-To: <5130651C.3010504@dallaway.org.uk>

OK, I finally had the time to get back to the migration...

I convinced Macraigor Systems to send me the libgcc.a they built with 
their cross-compiler.
With the correct libgcc.a I got the Win7 environment to link, finally.
The pieces:
* Cygwin 1.7.17
* eCos 1.3.1
* GNU arm-elf toolchain 4.6.0
* added compiler option -fno-use-cxa-atexit

After cleaning up hundreds of new compiler warnings I have a firmware 
build to test.

Thank you to all who gave suggestions.

Regards,

Christopher Biessener

P.S. To answer John, the old developers here left us an app called 
ARMELFINSTALLATION.EXE which would install the 2.95 toolchain.  That 
installer would not work on Win7.

Aside - I found the eCos 1.3.1 config file for our ARM7.  Is there a 
guide anywhere to assist in converting a 1.3.1 eCos config to eCos 3.0?  
I tried loading the old config in eCos 3.0 and got endless errors of 
unsupported options.

On 03/01/2013 02:21 AM, John Dallaway wrote:
> Hi Christopher
>
> On 28/02/13 18:25, Christopher Biessener wrote:
>
>> I am new to embedded systems and got handed the task of migrating our
>> build environment from win2k to win7.
>> In win2k they are using Cygwin 1.3 / eCos 1.3.1 / gcc 2.95 toolchain.
> [ snip ]
>
>> The arm-elf 2.95 toolchain will not install in win7, so I began
>> upgrading stuff.
> First of all, can you explain what you mean by "The arm-elf 2.95
> toolchain will not install in win7"? Is there an error during the
> toolchain installation process or does the toolchain not execute under
> Cygwin 1.7.x? What error message are you observing?
>
> Assuming that the toolchain does not execute, and given your objective
> of minimising change, I would suggest attempting to build the arm-elf
> 2.95 toolchain under Cygwin 1.7.x. That would deliver generated eCos
> application code identical to what you have been generating under Win2k.
> The (very old) instructions for building the arm-elf 2.95 toolchain for
> eCos under Cygwin are at:
>
>    http://ecos.sourceware.org/tools/win-arm-elf.html
>
> If you attempt to use a much more recent arm-elf toolchain to built eCos
> 1.3.1 sources, you will find quite a number of source code issues to
> work through.
>
> I hope this helps...
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
>


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

      parent reply	other threads:[~2013-03-13 21:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 20:32 [ECOS] " Christopher Biessener
2013-02-18 22:21 ` [ECOS] " Grant Edwards
2013-02-28 18:25   ` Christopher Biessener
2013-03-01  8:21     ` John Dallaway
2013-03-04 16:27       ` Grant Edwards
2013-03-13 21:32       ` Christopher Biessener [this message]

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=5140F07F.1080704@voomtech.com \
    --to=christopherpb@voomtech.com \
    --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).