public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Santiago Lafon - Controles S.A." <slafon@controles.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] error with __cxa_atexit and __dso_handle
Date: Fri, 14 Sep 2007 15:16:00 -0000	[thread overview]
Message-ID: <46EAA5B4.9060501@controles.com> (raw)

I want to upgrade my arm-alf toolchan to the latest GNU tools

Some time ago, i made a toolchain with:
     binutils 2.14
     gcc-core 3.3.1
     gcc-g++  3.3.1
     newlib   1.11.0
     insight  5.3

Now i made a new one with
     binutils 2.18
     gcc    4.2.1
     newlib    1.15.0
     insight    6.6

I can build ecos without apparent problems (i'm working with a simple 
eb40a target).

Then, when i try to make a simple application (or if i try to make ecos 
tests), it's when my problems appears.

I get lots of errors like this:

work/eCos/lib/eb40a/rom/eb40a_rom_sin_net_v00.20_install/lib/extras.o: 
In function `__static_initialization_and_destruction_0':
/opt/ecos-snap-2007-09-09/packages/io/fileio/current/src/misc.cxx:105: 
undefined reference to `__cxa_atexit'

/opt/ecos-snap-2007-09-09/packages/io/fileio/current/src/misc.cxx:125: 
undefined reference to `__cxa_atexit'
/opt/ecos-snap-2007-09-09/packages/io/fileio/current/src/misc.cxx:532: 
undefined reference to `__dso_handle'

Could someone help me?

Thanks
     Santiago Lafon

-- 
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:[~2007-09-14 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14 15:16 Santiago Lafon - Controles S.A. [this message]
2007-09-14 20:54 ` Brian Clausing
2007-09-20 12:04 ` Alexey Shusharin
2007-09-21 18:32   ` Santiago Lafon

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=46EAA5B4.9060501@controles.com \
    --to=slafon@controles.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).