From: Andrew Lunn <andrew@lunn.ch>
To: John Macdonald <john.macdonald@nautronix.co.uk>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] arm-elf-g++ problem
Date: Fri, 08 Jun 2007 05:37:00 -0000 [thread overview]
Message-ID: <20070607133054.GA16526@lunn.ch> (raw)
In-Reply-To: <1181222113.10765.12.camel@localhost>
On Thu, Jun 07, 2007 at 02:15:13PM +0100, John Macdonald wrote:
> Hello,
>
> I am trying to compile some software for the Atmel AT91 processor under
> eCos. However, I am having trouble with my compiler. I built the arm-elf
> toolchain using the instructions on the eCos website. I then used the
> eCos configtool to configure eCos for the default Atmel evaluation board
> (EB40). However, if I try to compile:
>
> //#include <stdio.h>
> #include <iostream>
>
> int main()
> {
>
> // printf("Hello\n\r");
> cout << "Hello\n";
>
> }
>
>
> Using the command:
>
> arm-elf-g++ -I /home/johnm/ecos-work/arm_install/include test1.cpp -c
>
>
> Then I get lots of errors. The included directory was produced by the
> eCos configtool. The first block of errors are:
>
> johnm@johnm-desktop:~/ecos_play$ arm-elf-g++
> -I /home/johnm/ecos-work/arm_install/include test1.cpp -c
> In file included
> from /home/johnm/ecos_toolchain/gnutools/arm-elf/include/arm-elf/bits/c
> ++io.h:35,
>
> from /home/johnm/ecos_toolchain/gnutools/arm-elf/include/bits/fpos.h:44,
>
> from /home/johnm/ecos_toolchain/gnutools/arm-elf/include/iosfwd:46,
>
> from /home/johnm/ecos_toolchain/gnutools/arm-elf/include/ios:44,
>
> from /home/johnm/ecos_toolchain/gnutools/arm-elf/include/ostream:45,
>
> from /home/johnm/ecos_toolchain/gnutools/arm-elf/include/iostream:45,
> from test1.cpp:2:
> /home/johnm/ecos_toolchain/gnutools/arm-elf/include/cstdio:129: `remove'
> not
> declared
> /home/johnm/ecos_toolchain/gnutools/arm-elf/include/cstdio:130: `rename'
> not
> declared
> /home/johnm/ecos_toolchain/gnutools/arm-elf/include/cstdio:137:
> `tmpfile' not
> declared
> /home/johnm/ecos_toolchain/gnutools/arm-elf/include/cstdio:138: `tmpnam'
> not
> declared
>
> If I comment out the C++ lines and comment in the C lines then an object
> file is successfully produced. Does anyone know what is wrong here.
The C++ support for eCos is somewhat limited in anonymous
CVS. iostream is one of the things which do not work. Search the
archive for mor details.
If you want full c++ support, you probably want to license one of the
commercial forks of eCos, eg from eCosCentric.
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:[~2007-06-07 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 18:18 John Macdonald
2007-06-08 5:37 ` Andrew Lunn [this message]
2007-06-08 10:59 ` Paul D. DeRocco
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=20070607133054.GA16526@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=john.macdonald@nautronix.co.uk \
/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).