Issue 47225 - Error while making "xmlsecurity" project OpenOffice.org 1.9_m91 (build 680)
Summary: Error while making "xmlsecurity" project OpenOffice.org 1.9_m91 (build 680)
Status: CONFIRMED
Alias: None
Product: Build Tools
Classification: Code
Component: solenv (show other issues)
Version: OOo 2.0
Hardware: All Windows XP
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 47226 (view as issue list)
Depends on:
Blocks:
 
Reported: 2005-04-12 09:19 UTC by hgkhai
Modified: 2013-02-07 21:50 UTC (History)
7 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
Patch to fix the problem (808 bytes, text/plain)
2008-04-07 01:07 UTC, greyham
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description hgkhai 2005-04-12 09:19:36 UTC
Dear all,
I have downloaded and tried to build with full option of OpenOffice.org 
1.9_m91 (build 680) but an error occured during build "xmlsecurity" project. 
Error description is as below:

c:\progra~1\micros~1.net\vc7\bin\cl.exe @C:\Temp\mk8
securityenvironment_mscryptimpl.cxx
d:\OOo_1.9.m91_src\xmlsecurity\source\xmlsec\mscrypt\securityenvironment_mscryp
timpl.hxx(126) : fatal error C1083: Cannot open include 
file: 'xmlsec/xmlsec.h': No such file or directory
dmake: Error code 130, while 
making '..\..\..\wntmsci10.pro\slo\securityenvironment_mscryptimpl.obj'
'---*tg_merge.mk*---'
ERROR: Error 65280 occurred while making 
D:\OOo_1.9.m91_src\xmlsecurity\source\xmlsec\mscrypt

Could any one help me to solve this problem?

Thanks and regards.
Hoang Khai
Comment 1 christianjunker 2005-07-20 13:27:28 UTC
*** Issue 47226 has been marked as a duplicate of this issue. ***
Comment 2 christianjunker 2005-07-20 13:33:06 UTC
same for me, breaks with m118. 
The needed xmlsec.h actually lies in
SRC680_m118\libxmlsec\download\xmlsec1-1.2.6.tar.gz .

started and moving over to tools project.
Comment 3 christianjunker 2005-07-20 13:41:56 UTC
I guess the problem is because the flag --disable-mozilla for configure has been
used. Because then, this happens when trying to build libxmlsec:
=============
Building project libxmlsec
=============
/cygdrive/d/OOosrc/SRC680_m118/libxmlsec
Mozilla disabled -> no nss -> no libxmlsec....
Comment 4 quetschke 2005-08-31 17:34:50 UTC
Subcomponent dmake is for problems in dmake, not with dmake ;)

I don't think issues@vi is working on this problem, reassigning.

I'm not sure if --disable-mozilla is supported at the moment. Rene ?
Comment 5 hjs 2005-09-13 16:03:51 UTC
AFAIK, you only have the chance to choose between:
- use system mozilla (not an option for windows)
- build mozilla yourself (takes some time but works quite nice on current
milestones)
- download prebuilded mozilla files
(<http://tools.openoffice.org/moz_prebuild/680/>)
Comment 6 rene 2005-09-13 16:11:06 UTC
--disable-mozilla *should* also be possible. 
Comment 7 hjs 2005-09-15 16:00:09 UTC
looks like it currently (m124) isn't. same error in xmlsecurity
Comment 8 hjs 2005-09-29 19:00:18 UTC
anyone volunteering to fix "--disable-mozilla" for windows? :-)
Comment 9 mtg 2005-11-21 16:15:54 UTC
It would be nice to add an error message to configure when run with
'--disable-mozilla' on windows. This would be a good stop gap solution until it
is properly supported.

I can possibly look into this if no-one else volunteers ebfore me ?
Comment 10 hjs 2006-06-08 16:03:49 UTC
doesn't look like. would you like to attach a patch to "configure.in"?
Comment 11 happy_peach 2006-11-23 07:35:50 UTC
enable-mozilla , the issue also error like this ~~can skip the step? use 
solver, and which step to start?
Comment 12 greyham 2008-04-07 01:07:26 UTC
Created attachment 52597 [details]
Patch to fix the problem
Comment 13 Mathias_Bauer 2008-04-24 10:53:20 UTC
As the Mozilla libs are not needed at all for signatures on Windows we should
adjust the patch to reflect that and moreover also patch the makefile.mk of
libxmlsec also. 

I hacked the makefile in xmlsec and was able to build it successfully even
without any traces of Mozilla in solver.