This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Linking errors with arm-elf-g++
- From: Andrew Lunn <andrew dot lunn at ascom dot ch>
- To: Ravi Joshi <ravijoshi at operamail dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Tue, 19 Aug 2003 15:36:21 +0200
- Subject: Re: [ECOS] Linking errors with arm-elf-g++
- References: <20030819132455.7537.qmail@operamail.com>
On Tue, Aug 19, 2003 at 06:54:55PM +0530, Ravi Joshi wrote:
> Dear all,
>
> I am trying to port Bluetoot protocol stack on EP7312 board from Cirrus Logic. I am using eCos-1.3.1 version on RedHat Linux 9.0.
>
> 1. The complete Bluetooth stack has been coded in plain C
>
> 2. I could successfully compile and port the stack on EP7312 board and also could run a sample application using arm-elf-gcc.
>
> 3. Now I am trying to compile the stack using arm-elf-g++.
Why?
gcc is a front end to the C compiler, the C++ compiler, the objective
C compiler, the Ada compiler etc. gcc stands for GNU Compiler
Collection. If you pass a C file to it, it will call the C
compiler. If you pass it a c++ file it will call the c++ compiler etc.
If you bypass gcc and call the wrong compiler directly, which is what
you are doing, its bound to go wrong.
Andrew
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss