To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=87098 Issue #|87098 Summary|Build breaks in openssl - code page issue Component|tools Version|DEV300m3 Platform|PC URL| OS/Version|Windows XP Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|mh Reported by|jeongkyu
------- Additional comments from [EMAIL PROTECTED] Sun Mar 16 21:28:54 +0000 2008 ------- I am trying to build DEV300_m3 with VC++ 2008 Express on *Korean version of Windows XP*. Unfortunately, it broke in openssl with following errors. ... .\crypto\x509v3\v3_pcia.c : error C2220: warning treated as error - no 'object' file generated .\crypto\x509v3\v3_pcia.c : warning C4819: The file contains a character that cannot be represented in the current code page (949). Save the file in Unicode format to prevent data loss NMAKE : fatal error U1077: 'c:\PROGRA~1\MICROS~1.0\VC\bin\cl.exe' : return code'0x2' Stop. dmake: Error code 2, while making './wntmsci11.pro/misc/build/so_built_openssl' ... I found the file has its authors name in header comment and Korean code page does not like it. In another modules, this usually gives warning but does not break build. However, openssl has more strict compile option which does not allow warning and it breaks build. To make build successful, I had to converting the encoding of the files below into cp949 (with discarding unconvertible characters). After fixing these files, openssl was built successfully. .\crypto\x509v3\v3_pci.c .\crypto\x509v3\v3_pcia.c Another solution for me was to change default system language. After changing it into en-US (and rebooting), the build of openssl could be done without errors. I believe this is a safe way to build OOo, but may be too much for some non-Western developer unless they have dedicated machine only for building OOo. The last option I can think of is to change compile option of openssl so that build does not break with warnings. I am not sure which is the best way to handle code page issue, but I believe it should be addressed somehow. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
