This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Failed compile on XP buildbot
Type: compile error Stage: resolved
Components: Build Versions: Python 3.3, Python 3.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: db3l, loewis, pitrou
Priority: high Keywords: buildbot

Created on 2013-05-08 12:03 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg188720 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-05-08 12:03
OpenSSL fails compiling on the XP-4 buildbot. Judging by the errors below (snipped), the nasm version may be too old (?) to understand some of the assembler instructions used in the source. David, could you perhaps take a look?

http://buildbot.python.org/all/buildslaves/bolen-windows


Build:
  cd "d:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\PCbuild\"
  "d:\cygwin\home\db3l\buildarea\3.x.bolen-windows\build\PCbuild\python_d.exe" build_ssl.py Release Win32 -a
  
  Found a working perl at 'c:\Perl\bin\perl.exe'
  Executing ssl makefiles: nmake /nologo -f "ms\nt.mak"
  Building OpenSSL
  	nasm -f win32 -o tmp32\sha1-586.obj tmp32\sha1-586.asm
  tmp32\sha1-586.asm:2646: warning: label alone on a line without a colon might be in error
  tmp32\sha1-586.asm:2647: error: parser: instruction expected
  tmp32\sha1-586.asm:2648: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2648: error: parser: instruction expected
  tmp32\sha1-586.asm:2649: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2649: error: parser: instruction expected
  tmp32\sha1-586.asm:2650: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2650: error: parser: instruction expected
  tmp32\sha1-586.asm:2651: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2651: error: parser: instruction expected
  tmp32\sha1-586.asm:2658: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2658: error: parser: instruction expected
  tmp32\sha1-586.asm:2659: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2659: error: parser: instruction expected
  tmp32\sha1-586.asm:2660: error: symbol `vmovdqa' redefined
  tmp32\sha1-586.asm:2660: error: parser: instruction expected
  tmp32\sha1-586.asm:2662: error: symbol `vmovdqa' redefined
msg188732 - (view) Author: David Bolen (db3l) * Date: 2013-05-08 18:59
Yeah, the XP buildbot was pretty old, at nasm 2.02, so I updated to the same 2.09 as the Win7 buildbot, restarted the last build and it went through compilation fine.

However, then it failed in test_ssl, and in checking, it looks like my Win7 buildbot is failing the same way.  I thought it might just be an independent problem, but then found issue 15172 from last June (like Jeremy I have 2.09.02) which seems to say OpenSSL 1.0.1+ needs nasm 2.10.  In Jeremy's case it only affected his 64-bit build, so maybe that's why I haven't seen it yet, but perhaps with the recent move to 1.0.1d it can affect 32-bit as well?

Ah, or wait, there's also issue 17425 that seems to indicate 1.0.1d may be at fault for that test failure.

Anyway, I installed the latest nasm 2.10.07 both both XP and Win7, and flushed the openssl tree in the 3.3 and 3.x build branches.  In retrying the XP 3.x build it still fails test_ssl, so I don't think there's anything else I can change on the buildbot side as it looks like fixing that needs us to switch to 1.0.1e
msg188734 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2013-05-08 19:11
Yes, the test_ssl failure is orthogonal. Thanks for fixing the compile issue!
History
Date User Action Args
2022-04-11 14:57:45adminsetgithub: 62135
2013-05-08 19:11:40pitrousetstatus: open -> closed
resolution: fixed
messages: + msg188734

stage: resolved
2013-05-08 18:59:51db3lsetmessages: + msg188732
2013-05-08 12:03:24pitroucreate