[C++-sig] status of auto-builds

[David Abrahams]

----- Original Message -----
From: "Ralf W. Grosse-Kunstleve" <rwgk at yahoo.com>
To: <c++-sig at python.org>
Sent: Tuesday, July 02, 2002 5:57 PM
Subject: Re: [C++-sig] status of auto-builds


> --- David Abrahams <david.abrahams at rcn.com> wrote:
> > it's a simple matter of the boost/config/suffix.hpp file detecting
> > the value for BOOST_HAS_LONG_LONG differently in two different
translation
> > units. In libs/python/src/builtin_converters.cpp the test is coming up
> > negative, while in libs/python/test/test_builtin_converters.cpp it's
coming
> > up positive. If you can find out which file is defining any of the
> > following symbols
> >
> >     ULLONG_MAX
> >     ULONG_LONG_MAX
> >     ULONGLONG_MAX
> >
> > then we will be close to having the problem solved. I've been
approaching
> > it by taking the command-line which builds test_builtin_converters.o
(get
> > that from bjam... -n -a test_builtin_converters.o) and
> > adding -DULLONG_MAX -DULONG_LONG_MAX -DULONGLONG_MAX so it would tell
me
> > where the conflicting definition is.
>
> Done. The cxx 6.5 compiler does not seem to mind at all what these
defines are
> (I tried -DULLONG_MAX=jibberjabber -DULONG_LONG_MAX=dingdong
> -DULONGLONG_MAX=klickklack). But the runtime errors are still there.
> This is with the CVS state from less than an hour ago.
> Ralf

You compiled both translation units specified above with these defined?

It must be something else, then. Time to break out the debugger, Ralf (I
know how you love to hear that)!