[ python-Bugs-1672336 ] Building python 2.5 for AMD64 (windows) and VS2005

SourceForge.net noreply at sourceforge.net
Sat Mar 3 14:13:33 CET 2007


Bugs item #1672336, was opened at 2007-03-02 11:16
Message generated for change (Comment added) made by krisvale
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1672336&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: fred2k (fred2k)
Assigned to: Kristján Valur (krisvale)
Summary: Building python 2.5 for AMD64 (windows) and VS2005

Initial Comment:
When building pythoncore for AMD64 (WIndows) on VS2005, I get the following error : 

3>generate buildinfo
3>cl.exe -c -D_WIN32 -DUSE_DL_EXPORT -D_WINDOWS -DWIN32 -D_WINDLL -MD -MD /USECL:MS_OPTERON ..\Modules\getbuildinfo.c -Fogetbuildinfo.o -I..\Include -I..\PC
3>Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.42 for 80x86
3>Copyright (C) Microsoft Corporation.  All rights reserved.
3>getbuildinfo.c
3>Linking...
3>LINK : warning LNK4044: unrecognized option '/USELINK:MS_SDK'; ignored
3>getbuildinfo.o : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
3>Build log was saved at "file://d:\users\fbr\python build\Python-2.5\PCbuild8\amd64-temp-release\pythoncore\BuildLog.htm"
3>pythoncore - 1 error(s), 225 warning(s)

I already looked for the issue on google and on the ML archive (http://mail.python.org/pipermail/python-dev/2006-March/062753.html) but the workaround explained there (checking vsextcompiler) is specific for VC2003.

Has anyone solved this problem ?







----------------------------------------------------------------------

>Comment By: Kristján Valur (krisvale)
Date: 2007-03-03 13:13

Message:
Logged In: YES 
user_id=1262199
Originator: NO

Ok, I will look into this when I get the oppertunity.  Possibly these .sln
file or .vcproj have gotten contaminated with some strange options...

----------------------------------------------------------------------

Comment By: fred2k (fred2k)
Date: 2007-03-03 12:08

Message:
Logged In: YES 
user_id=1733250
Originator: YES

As I tried to build with MVS2005, I used the sln file in the PCBuild8
directory

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2007-03-03 12:05

Message:
Logged In: YES 
user_id=21627
Originator: NO

In what directory? PCbuild or PCbuild8?

----------------------------------------------------------------------

Comment By: fred2k (fred2k)
Date: 2007-03-03 11:53

Message:
Logged In: YES 
user_id=1733250
Originator: YES

What do you mean by PCBuild8 build setup ??
I only see the files that are necessary to the build in the directory.

----------------------------------------------------------------------

Comment By: Kristján Valur (krisvale)
Date: 2007-03-03 10:57

Message:
Logged In: YES 
user_id=1262199
Originator: NO

This suggest to me that the reporter is not using the PCBuild8 build setup
to do this, since that should have all-new flags.  I will still try to
repro, though.

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2007-03-03 10:40

Message:
Logged In: YES 
user_id=21627
Originator: NO

USECL and USELINK is easily resolved: that's an option of vsextcomp, used
to build the "official" AMD64 and Itanium binaries with the 2003 build
environment, vsextcomp, and the platform compilers. Apparently, when the VS
2005 projects were created, the AMD64 and Itanium targets weren't updated.

----------------------------------------------------------------------

Comment By: Kristján Valur (krisvale)
Date: 2007-03-03 10:23

Message:
Logged In: YES 
user_id=1262199
Originator: NO

Well, it sounds like he is trying to link modules compiled for different
machines.
/USECL or /USELINK aren't options for MSVC, so something fishy is going on
there.  I will try to reproduce when I get the chance

----------------------------------------------------------------------

Comment By: Martin v. Löwis (loewis)
Date: 2007-03-03 01:49

Message:
Logged In: YES 
user_id=21627
Originator: NO

Kristjan, can you take a look? If not, please unassign.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1672336&group_id=5470


More information about the Python-bugs-list mailing list