This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: arm-elf-gcc, arm-elf-g++, arm-elf-c++

To: "Richard Slaughter" <rslaughter at anatel dot com>,<crossgcc at sourceware dot cygnus dot com>
Subject: Re: arm-elf-gcc, arm-elf-g++, arm-elf-c++
From: "Dave Korn" <davek-ml at ntlworld dot com>
Date: Wed, 31 Oct 2001 01:41:05 -0000
References: <004101c1619f$5e618bf0$740aa8c0@richards>
Reply-To: "Dave Korn" <davek-ml at ntlworld dot com>

----- Original Message -----
From: "Richard Slaughter" <rslaughter@anatel.com>
To: <crossgcc@sourceware.cygnus.com>
Sent: Wednesday, October 31, 2001 12:02 AM
Subject: arm-elf-gcc, arm-elf-g++, arm-elf-c++

> David,
> you just confused me.. easy to do..
> what is the difference between arm-elf-gcc, arm-elf-g++, arm-elf-c++?
> I've been using arm-elf-gcc.

The g++ driver presents different options to the compiler and the linker
than the gcc driver, and different predefines to the preprocessor.  For
example, g++ automatically adds '-lstdc++' to any command line but gcc
doesn't.  I suspect that it needs to add some options to make the C++
exception handling and stack unwinding stuff work right, and if you use g++
(I think c++ will be the same as g++) you may find your problems magically
disappear.

    DaveK
--
Burn your ID card!  http://www.optional-identity.org.uk/
Help support the campaign, copy this into your .sig!

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

References:
- arm-elf-gcc, arm-elf-g++, arm-elf-c++
  - From: Richard Slaughter

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]