Re: [Boost-build] [darwin][jam][g++-4.2] darwin build command adds '-Wno-long-double', unsupported in Mac gcc?

Subject: Re: [Boost-build] [darwin][jam][g++-4.2] darwin build command adds '-Wno-long-double', unsupported in Mac gcc?
From: Vladimir Prus (ghost_at_[hidden])
Date: 2009-02-19 02:38:53

On Thursday 19 February 2009 10:08:47 Dean Michael Berris wrote:
> On Thu, Feb 19, 2009 at 2:56 PM, Vladimir Prus <ghost_at_[hidden]> wrote:
> > On Thursday 19 February 2009 09:21:44 Dean Michael Berris wrote:
> >> On Thu, Feb 19, 2009 at 2:09 PM, Vladimir Prus <ghost_at_[hidden]> wrote:
> >> > On Thursday 19 February 2009 07:34:01 Dean Michael Berris wrote:
> >> >>
> >> >> Am I missing anything obvious? If not, how do I go about addressing this?
> >> >
> >> > You should download the nightly build from boost.org/boost-build2, which has
> >> > a fix for this problem.
> >> >
> >>
> >> Thanks. That sounds fine -- can I standardize on *a* nightly build
> >> that I can rely on to be "stable"? Or should I wait for the package
> >> release of Boost 1.39 to get that "stable" version?
> >
> > In practice, you can pick any nightly build, and don't upgrade until you
> > need some new feature of bug fix. The version in 1.39 is essentially a random
> > nightly build.
> >
> 
> Okay, that sounds great. :-)
> 
> I tried the latest nightly build though, and I still encounter the
> problem with the 4.2 compiler. Apparently '-Wno-long-double' is still
> defined even for that version. With the 4.0 compiler though it appears
> to be working fine.

This is strange. Can you open tools/darwin.jam and find code that looks
like this:

    # - GCC 4.2 and higher in Darwin does not have -Wno-long-double.
    if $(version) < "4.2.0"
    {
        flags darwin.compile OPTIONS $(condition) : -Wno-long-double ;
    }

Modify it to read:

    # - GCC 4.2 and higher in Darwin does not have -Wno-long-double.
    ECHO "XXXXXXXXXXXXX " $(version) ;
    if $(version) < "4.2.0"
    {
        flags darwin.compile OPTIONS $(condition) : -Wno-long-double ;
    }

and report what is printed. If nothing is printed, it means you're not
actually using the nightly build you've downloaded. Otherwise, we should
be able to understand why the condition fails to work.

Thanks,
Volodya