From: Martin Buck <martin.buck@ascom.ch>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Problem while building the ecos Application with newer version gcc tool set.
Date: Tue, 11 Jun 2002 09:22:00 -0000 [thread overview]
Message-ID: <3D0623B7.23F17685@ascom.ch> (raw)
In-Reply-To: <200206111031.15976.tdrury@siliconmotorsports.com>
Tim Drury wrote:
> Search the mailing list archives for "cannot find libsupc++.a" and you'll find
> the answer. I think someone posted the answer again just yesterday.
> It involves removing libsupc++ from the target.ld file.
No, it doesn't (at least not if you want to write C++ code). It involves
building and installing libsupc++:
http://sources.redhat.com/ml/ecos-discuss/2001-10/msg00274.html
Martin
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2002-06-11 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 7:23 jameshq
2002-06-11 7:29 ` Andrew Lunn
2002-06-11 7:34 ` jameshq
2002-06-11 7:38 ` Andrew Lunn
2002-06-11 8:10 ` jameshq
2002-06-11 7:31 ` Tim Drury
2002-06-11 9:22 ` Martin Buck [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=3D0623B7.23F17685@ascom.ch \
--to=martin.buck@ascom.ch \
--cc=ecos-discuss@sources.redhat.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).