Re: BUG: CommonC++ includes compile time $CFLAGS in ccgnu2-config --flags

[David Sugar]

I have already checked in a new branch in cvs, -r stable2, to start 
sorting this and other issues out in for future releases starting with 
1.3....


Curtis Magyar wrote:

> On Sat, 2004-07-31 at 10:14 -0400, David Sugar wrote:
>  
>
> > I believe at the time the intent was to make sure that anything 
> > decendent from common c++ was also compiled with the same options.  This 
> > is important for some options, such as exception handling, but may cause 
> > issues with source build systems for others.  One problem is that a 
> > number of Common C++ specific options detected and set in the configure 
> > script, such as rtti settings, are currently set against CXXFLAGS rather 
> > than something seperate THREAD_FLAGS, and hence would also be lost with 
> > this patch.
> >    
>
> It also seems to break libccext2.pc, because the header directory isn't
> specified.  :(
>
>
>  
>
> > I think the best solution would be to rework the configure tests to 
> > assure those compiler options which are set through tests always do make 
> > it into what ccgnu2-config --flags exports, and those things set by 
> > presetting CFLAGS/CXXFLAGS in front of configure do not.  Since these 
> > tested options are not related to threading itself. they probably should 
> > be represented with COMMMON_FLAGS rather than THREAD_FLAGS, so they are 
> > easier to identify.  Then ccgnu2-config --flags would export the value 
> > of THREAD_FLAGS & COMMON_FLAGS rather than THREAD_FLAGS & CXXFLAGS as it 
> > does now.
> >    
>
> I spent some time playing with the configure.in last night.  I'll
> explore some more, and familiarize with the m4 stuff.  Hopefully I can
> be of some help in straightening this out.
>
> --
> Curtis Magyar
>
>
>