public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Biessener <christopherpb@voomtech.com>
To: Ecos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] migration from win2k to win7
Date: Mon, 18 Feb 2013 20:32:00 -0000	[thread overview]
Message-ID: <51228FE9.1030605@voomtech.com> (raw)

Hi all,

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.  
This setup compiles and links and our hardware runs beautifully.  We 
can't keep limping along on win2k, however.

The arm-elf 2.95 toolchain will not install in win7, so I began 
upgrading stuff.
So far I have the newest Cygwin 1.7 - which uses gcc 4.5.3.  I 
downloaded the arm-elf toolchain via MacCraigor Systems website which is 
gcc 4.6.0.  I cannot find the arm-elf toolchain in any other rev-level.
Apparently eCos 1.3.1 is still viable and it did install on win7, so 
that is what I used.
I am afraid of upgrading to eCos 3.0 because I have no idea what 
configuration options were used.  There is no documentation the original 
developers left - and yes, they are long gone.

At first gcc couldn't find libgcc, so I added 
-L/usr/lib/gcc/i686-pc-cygwin/4.5.3 to the link flags.
Without further changing our makefiles everything compiled, but it will 
not link.  The following is part of the output of make:
----------------------
arm-elf-gcc -mcpu=arm7tdmi -u cyg_user_start 
-Wl,'-Map=HC3-P_Hw_Cf_P1.map'  -nostartfiles  -Wl,--gc-sections 
-L./romram_install/lib  -L/usr/lib/gcc/i686-pc-cygwin/4.5.3 -o 
HC3-P_Hw_Cf_P1.elf libHC3-P_Hw_Cf_P1.a libromHC3-P_Hw_Cf_P1.a 
-TtargetHC3-P_Hw_Cf_P1.ld  -nostdlib
libromHC3-P_Hw_Cf_P1.a(HardCopy.o): In function 
`__static_initialization_and_destruction_0(int, int)':
HardCopy.cpp:(.text._Z41__static_initialization_and_destruction_0ii+0x48): 
undefined reference to `__cxa_atexit'
HardCopy.cpp:(.text._Z41__static_initialization_and_destruction_0ii+0x60): 
undefined reference to `__dso_handle'
libromHC3-P_Hw_Cf_P1.a(fat32.o): In function 
`CFAT32::InitBootSector(FAT32_BOOT_SECTOR*, FAT32_FSINFO_SECTOR*)':
fat32.cpp:(.text._ZN6CFAT3214InitBootSectorEP17FAT32_BOOT_SECTORP19FAT32_FSINFO_SECTOR+0x118): 
undefined reference to `__umodsi3'
fat32.cpp:(.text._ZN6CFAT3214InitBootSectorEP17FAT32_BOOT_SECTORP19FAT32_FSINFO_SECTOR+0x150): 
undefined reference to `__udivsi3'
----------------------

Any suggestions would be greatly appreciated.  I did begin by searching 
the list archive.  There were no solutions to be found.

Thanks,

Christopher Biessener
Voom Technologies, Inc.


-- 
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:[~2013-02-18 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 20:32 Christopher Biessener [this message]
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

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=51228FE9.1030605@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).