This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: C vs C++ compilations
- From: Bart Veer <bartv at ecoscentric dot com>
- To: gary at mlbassoc dot com
- Cc: ecos-devel at ecos dot sourceware dot org
- Date: Wed, 15 Oct 2003 14:57:45 +0100 (BST)
- Subject: Re: C vs C++ compilations
- References: <1066224867.32461.16.camel@hermes>
>>>>> "Gary" == Gary Thomas <gary@mlbassoc.com> writes:
Gary> I'm experimenting with GCC-3.3. This version is starting to be
Gary> *really* picky about some things. In particular, the eCos Makefile(s)
Gary> use XX-gcc to compile either C or C++ source files, often with
Gary> some C++ only flags thrown in. This leads to warnings like this:
Gary> cc1: warning: "-Woverloaded-virtual" is valid for C++ but not for C/ObjC
Gary> cc1: warning: "-fno-rtti" is valid for C++ but not for C/ObjC
Gary> cc1: warning: "-fvtable-gc" is valid for C++ but not for C/ObjC
Gary> I'd like to get rid of these and the best way [I think] would be
Gary> to change the rules so that C files are built using XXX-gcc using
Gary> C flags and C++ files are built using XXX-g++ with C++ flags. I
Gary> also think that over time, the compiler may decide that this is no
Gary> longer just a warning, but an error, so thinking about this now will
Gary> save us in the future.
Gary> Is there any [good] way to handle this? Can the Makefile generator
Gary> (CDL machine) be set up to handle both C and C++ (probably CXXFLAGS)?
Gary> Thanks.
Gary> Note: it works perfectly well, it's just noisy at the moment.
See bugzilla 1000035. Andrew has already tried a patch which looked
fine, but caused problems with arm builds.
Bart