Build problem, PythonTest_pyuno_pytests_ssl fails

[Michael Stahl]

On 16.01.2015 13:35, Pavel Laštovička wrote:
> Hello,
> 
> Dne 9.1.2015 v 10:11 Caolán McNamara napsal(a):
>> On Mon, 2014-12-15 at 17:11 +0100, Pavel Laštovička wrote:
>>>
>>> But by trial and error I found python fails on the following line:
>>>
>>>       import _ssl
>>>
>>> Meanwhile, I have decided to remove this python check so I can continue with building.
>> That test ensures that the email mail merge has ssl support. Maybe you
>> have *another* _ssl.so in your path somewhere which is detected somehow
>> before the one that is built as part of LibreOffice.
>>
>> C.
> 
> so with debugging I have found the cause of failed "import ssl":
> 
> 'python.exe': Loaded 'C:\WINDOWS\system32\rsaenh.dll'
> 'python.exe': Loaded 'D:\LO\instdir\program\python3.dll', Binary was not built with 
> debug information.
> 'python.exe': Loaded 'D:\LO\instdir\program\python-core-3.3.3\lib\_ssl.pyd', Symbols 
> loaded.
> 'python.exe': Loaded 'C:\WINDOWS\system32\ws2_32.dll'
> 'python.exe': Loaded 'C:\WINDOWS\system32\ws2help.dll'
> 'python.exe': Loaded 'C:\WINDOWS\system32\libeay32.dll', Binary was not built with 
> debug information.
> 'python.exe': Loaded 'C:\WINDOWS\system32\wsock32.dll'
> 'python.exe': Loaded 'C:\WINDOWS\system32\msvcr71.dll'
> First-chance exception at 0x7c9673be (ntdll.dll) in python.exe: 0xC0000138: Ordinal 
> Not Found.
> 
> Python has a problem that if a required DLL exists in one of two Windows 
> directories, LoadLibraryEx API uses it instead of DLL with the same name in 
> LibreOffice program directory. I thought about how this could be fixed but only 
> solution I have found is to copy libeay32.dll and ssleay32.dll into Python's lib 
> directory. As we cannot assume what an user might or might not have installed in his 
> Windows directory.

can you find out which application is insane and anti-social enough to
install libeay32.dll in the windows system directory and file a bug
against it?  with Win32 LoadLibrary doing what it does, it probably
breaks more applications than just LO.

in this case not even the upcoming merging of URE and OOO layers in LO
4.5 is going to help since _ssl.pyd is in a subdirectory.

> Import ssl works for me now but the respective unittest still fails for some reason. 
> It would be much easier to fix if LO's Python would not have broken stdout (maybe it 
> happens only on Windows, I have not tested Linux).

instdir/program/python.exe prints fine in my (weeks old) master build
(when run in cmd.exe)