From: Gary Thomas <gary@mlbassoc.com>
To: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Linker Problem with Codesourcery lite arm-none-eabi 4.6.1
Date: Sun, 04 Mar 2012 13:09:00 -0000 [thread overview]
Message-ID: <4F536972.8060206@mlbassoc.com> (raw)
In-Reply-To: <4F5366DD.4030908@gmail.com>
On 2012-03-04 05:58, Bob Brusa wrote:
> Hi
> the linker produces the following message:
>
> arm-none-eabi-g++ -LC:\ProjDAc\TDSsw\libs\tds_lib_2_install\lib -TC:\ProjDAc\TDSsw\libs\tds_lib_2_install\lib\target.ld -mcpu=arm7tdmi -Wl,--gc-sections -Wl,-static -nostdlib
> -mno-thumb-interwork -Xlinker -Map -Xlinker tds_4.Map -otds_4.elf usb_cdc.o tds_sym.o pa.o
> c:/programme/codesourcery/sourcery_codebench_lite_for_arm_eabi/bin/../lib/gcc/arm-none-eabi/4.6.1/../../../../arm-none-eabi/lib\libsupc++.a(vterminate.o): In function
> `__gnu_cxx::__verbose_terminate_handler()':
> vterminate.cc:(.text._ZN9__gnu_cxx27__verbose_terminate_handlerEv+0x184): undefined reference to `_impure_ptr'
> collect2: ld returned 1 exit status
> Build error occurred, build is stopped
> Time consumed: 3562 ms.
>
> Unfortunately, this "diagnostics" does not offer a clue on the source of the problem. Sure, somewhere in my source, but where and what? Does someone have a helpful advice?
> Thanks - Bob.
>
Note: this has been discussed a lot in the archives...
http://bit.ly/xpp3d4
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2012-03-04 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 12:58 Bob Brusa
2012-03-04 13:09 ` Gary Thomas [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=4F536972.8060206@mlbassoc.com \
--to=gary@mlbassoc.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).