From: Andrew Lunn <andrew@lunn.ch>
To: David Fernandez <dfernandez@cct.co.uk>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Problems building ecos sources
Date: Wed, 22 Feb 2006 16:54:00 -0000 [thread overview]
Message-ID: <20060222165331.GI3433@lunn.ch> (raw)
In-Reply-To: <1140626982.2878.16.camel@software.cct.co.uk>
On Wed, Feb 22, 2006 at 04:49:42PM +0000, David Fernandez wrote:
>
> Hi there,
>
> I'm trying to configure and make the gcc-2.0 tarball, but gives several
> warnings about compiler options not supported for C++, and finally it
> stops complaining about undefined dinamic linker symbols.
>
> I'm using gcc-4.0.2 toolchain, does it support that?
>
> Any ideas about what could be wrong?
So you are using gcc-4.0.2 to compile gcc-2.0? Why do you want to use
such an old version of gcc?
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-02-22 16:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 16:49 David Fernandez
2006-02-22 16:54 ` Andrew Lunn [this message]
[not found] ` <1140627369.2878.18.camel@software.cct.co.uk>
2006-02-22 21:39 ` Andrew Lunn
2006-02-23 11:33 ` David Fernandez
2006-02-23 15:02 ` Andrew Lunn
2006-02-23 15:37 ` David Fernandez
2006-02-23 15:51 ` Andrew Lunn
2006-02-23 16:48 ` [ECOS] " John Dallaway
[not found] ` <1140716284.2885.45.camel@software.cct.co.uk>
2006-02-24 6:11 ` Andrew Lunn
2006-02-24 16:38 ` David Fernandez
2006-02-24 17:14 ` Andrew Lunn
2006-02-24 22:00 ` [ECOS] " David Fernandez
2006-02-26 5:19 ` Andrew Lunn
2006-02-27 10:09 ` David Fernandez
2006-02-27 11:25 ` Andrew Lunn
2006-02-27 15:35 ` David Fernandez
[not found] ` <1141032779.2878.13.camel@software.cct.co.uk>
2006-02-27 18:14 ` Andrew Lunn
2006-02-27 22:48 ` David Fernandez
2006-05-14 2:51 ` Frank Pagliughi
2006-02-26 23:13 ` Chuck McManis
2006-02-27 9:33 ` David Fernandez
2006-02-23 17:30 ` Andrew Lunn
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=20060222165331.GI3433@lunn.ch \
--to=andrew@lunn.ch \
--cc=dfernandez@cct.co.uk \
--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).