Re: [boost] Newbie Trying to Build Boost Libraries on 64-bit MS WindowsVista

From: Beverly Pope (countryone77_at_[hidden])
Date: 2008-07-14 09:25:34

>From what I've been reading, the -sTools option is an older way of doing things and I've had a lot of trouble building with 64-bit.  I'll try using --address-model=64.
 
I'll try ignoring the warnings, per your suggestion.
 
I searched on the web and found that for Python 2.5, and found that:
int ilow = 0, ihigh = INT_MAX;
should be changed to:
Py_ssize_t ilow = 0, ihigh = PY_SSIZE_T_MAX;
It compiled after that change.  
 
I now have a problem with it finding a library, but I'll look at it some more before posting about that.
 
Thanks very much for your help.
Bev
Date: Tue, 8 Jul 2008 13:56:57 -0500
From: "Stephen Nuchia" <snuchia_at_[hidden]>
Subject: Re: [boost] Newbie Trying to Build Boost Libraries on 64-bit
        MS	WindowsVista
To: <boost_at_[hidden]>
Message-ID:
        <E763352EB1BA7547BBBC18A6980EBCB20171B05F_at_[hidden]>
Content-Type: text/plain;	charset="iso-8859-1"

> From: Beverly Pope [mailto:countryone77_at_[hidden]] 
???
I'm not familiar with the -sTools trick, I use --address-model=64 to get
64-bit builds.  I've not built with Python so I can't address those
errors in detail but I am familiar with the error message from other source
codes.
?
?
> 1) I see numerous (21360) warnings 
I have not investigated but I suspect it is impossible to suppress
this warning in the header that is responsible for it without leaving it
suppressed outside that header.  I recommend ignoring it.

> 2) When building the libraries, I get the following errors
[...]
>  error C2664: '_PyEval_SliceIndex' : cannot convert parameter
> 2 from 'int *' to 'Py_ssize_t *'
>??????? Types pointed to are unrelated; conversion requires
>        reinterpret_cast, C-style cast or function-style cast
[...]

This error message is triggered by a code flaw that is at least potentially
very dangerous.  ...
-swn