On Monday, September 21, 2015 at 9:54:51 AM UTC-7, Robin Becker wrote: > ......... > > > > This also sounds like the C++ stuff just wasn't installed. I'm afraid > > reinstallation is probably your best bet. > > > I used the default installation, but it failed first time around (perhaps a > network thing) and I stupidly assumed 'repair' would work. > > After a full reinstallation at least vcvarsall is present and I can at least > get the amd64/x86 compilers to work with bdist_wheel (I didn't get any errors > from using my already compiled relocatable libs) and I can no build the open > source reportlab extensions. > > One simple extension > > https://bitbucket.org/rptlab/pyrxp > > doesn't get built. For some reason I get a hang in the linker for both amd64 > & > x86. This builds fine for 27, 33 & 34. > > > However, I see this in the output > > | creating C:\ux\XB33\repos\pyRXP\build\lib.win-amd64-3.5 > | C:\Program Files (x86)\Microsoft Visual Studio > 14.0\VC\BIN\amd64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL > /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:\ux\XB33\py35_amd64\libs > /LIBPATH:C:\python35\libs /LIBPATH:C:\python35 > /LIBPATH:C:\ux\XB33\py35_amd64\PCbuild\amd64 "/LIBPATH:C:\Program Files > (x86)\Microsoft Visual Studio 14.0\VC\LIB\amd64" > "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio > 14.0\VC\ATLMFC\LIB\amd64" "/LIBPATH:C:\Program Files (x86)\Win > dows Kits\10\lib\10.0.10150.0\ucrt\x64" "/LIBPATH:C:\Program Files > (x86)\Windows > Kits\NETFXSDK\4.6\lib\um\x64" "/LIBPATH > :C:\Program Files (x86)\Windows Kits\8.1\lib\winv6.3\um\x64" wsock32.lib > /EXPORT:PyInit_pyRXPU build\temp.win-amd64-3.5\ > Release\ux\XB33\repos\pyRXP\src\pyRXP.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\xmlparser.obj bui > ld\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\url.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\s > rc\rxp\charset.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\string16.obj > build\temp.win-amd64-3.5\Re > lease\ux\XB33\repos\pyRXP\src\rxp\ctype16.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\dtd.obj build > \temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\input.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\s > rc\rxp\stdio16.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\system.obj > build\temp.win-amd64-3.5\Rele > ase\ux\XB33\repos\pyRXP\src\rxp\hash.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\version.obj > build\ > temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\namespaces.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyR > XP\src\rxp\http.obj > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\rxp\nf16check.obj > build\temp.win-amd64-3.5\ > Release\ux\XB33\repos\pyRXP\src\rxp\nf16data.obj > /OUT:build\lib.win-amd64-3.5\pyRXPU.cp35-win_amd64.pyd /IMPLIB:build\te > mp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\pyRXPU.cp35-win_amd64.lib > > | pyRXP.obj : warning LNK4197: export 'PyInit_pyRXPU' specified > multiple times; using first specification > | Creating library > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\pyRXPU.cp35-win_amd64.lib > > and ob > ject > build\temp.win-amd64-3.5\Release\ux\XB33\repos\pyRXP\src\pyRXPU.cp35-win_amd64.exp > > > | Generating code > Stderr: | error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio > 14.0\\VC\\BIN\\amd64\\link.exe' failed with > exit status 1 > > so there are some warnings which I don't understand. Maybe I need to do > something special for pyRXP (possibly I have some ifdefs poorly configured). > -- > Robin Becker
How long did you let it "hang"? For me the incremental linker took in the order of 30 minutes to link. I mentioned this on the Python issue tracker at <http://bugs.python.org/issue24872#msg249589>. -- https://mail.python.org/mailman/listinfo/python-list
