Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-18 Thread Martin v. Lšwis
> Martin, you've changed externals/bsddb-4.4.20 with regards to x64 > builds recently -- have you been able to get things working in your > x64 environments? I changed the project files so that it will use the x64 compilers even if no environment variables were set - the original bsddb files expec

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-18 Thread Martin v. Lšwis
> The other query I had was whether or not I should try a later version > of BerkeleyDB -- are we committed to 4.4.20 (or 4.4.x?) for 2.6/3.0 > or is it worth investigating newer versions? Martin/Jesus, any > thoughts on this? As Greg says: 4.5.x should work fine. Importing a new version into th

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-14 Thread Martin v. Lšwis
> I reviewed all the compiler options used by db_static.vcproj -- the > only thing I needed to bring over was -DDIAGNOSTIC for debug builds. > Everything else either had no impact and could be safely dropped, or > conflicted with compiler options used by the rest of the python build > (function lev

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-14 Thread Trent Nelson
> > Removing the dependency on db_static.vcproj and merging the relevant > > source code files into _bsddb.vcproj did the trick -- all x64 > > bsddb-related tests now pass. The only issue with this approach is > > that it locks _bsddb.vcproj into 4.4.20. However, considering that > > this approac

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-14 Thread Martin v. Lšwis
> Removing the dependency on db_static.vcproj and merging the relevant > source code files into _bsddb.vcproj did the trick -- all x64 > bsddb-related tests now pass. The only issue with this approach is > that it locks _bsddb.vcproj into 4.4.20. However, considering that > this approach (i.e. br

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-13 Thread Trent Nelson
Ah, and to think I just fixed 4.4.20 ;-) Removing the dependency on db_static.vcproj and merging the relevant source code files into _bsddb.vcproj did the trick -- all x64 bsddb-related tests now pass. The only issue with this approach is that it locks _bsddb.vcproj into 4.4.20. However, con

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-13 Thread Gregory P. Smith
On 3/13/08, Trent Nelson <[EMAIL PROTECTED]> wrote: > > Hey Greg, > > I'm at PyCon indeed, staying through the sprints 'til next Thursday. I'll > drop you a note offline re catching up. > > The other query I had was whether or not I should try a later version of > BerkeleyDB -- are we committed to

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-13 Thread Trent Nelson
Hey Greg, I'm at PyCon indeed, staying through the sprints 'til next Thursday. I'll drop you a note offline re catching up. The other query I had was whether or not I should try a later version of BerkeleyDB -- are we committed to 4.4.20 (or 4.4.x?) for 2.6/3.0 or is it worth investigating ne

Re: [Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-13 Thread Gregory P. Smith
I haven't built the bsddb stuff on windows myself in a few years and have never had access to a windows x64 system so I'm no silver bullet. Making the BerkeleyDB compile and link options match with those of python is the first place I'd start. Also you should be able to make a debug build of Berk

[Python-Dev] Windows x64 & bsddb 4.4.20 woes

2008-03-13 Thread Trent Nelson
I've been trying to give the Windows x64 builds a bit of TLC the past few evenings. I managed to get a successful build with all external modules last night (Tcl/Tk required about a half a dozen code/configuration changes each in order to build in a Windows x64 environment with Visual Studio 9,