Apache OpenOffice (AOO) Bugzilla – Issue 26436
The build breaks with "Error code 140, while making 'checkit'"
Last modified: 2013-02-24 21:08:20 UTC
Hello, I hope I am posting this to the right place... I am doing a full dmake on the 1.1.0 code and then I get an error message while doing odk/pack/checkbin See the attach snapshot of the window. My question is: What should I look for ? and if this is not the right place to place this issue - where should I post it ? I am trying to build the whole tree on Windows XP. Thank you, Ehood
Created attachment 13767 [details] Snapshot of the build window showing the problem
SW->MH: please have a look at this. Since I don't know which component has to be chosen for the build environment I left it on api, please change it appropriately.
mh->jsc: do you have an idea what's going wrong here ?
At this point a first content check of the SDK package is made. In your case the generation of the C++ UNO runtime reference hasn't worked. The check tests if several expected directories are existent, if not an error is genrated. Delete your output tree and try again. A newer version of this check script should print out a more detailed error description.
Hi, Sorry I am a newbee. I deleted all the tree and redownload the 1.1.0 source tree and then dmake all. I got the same problem again - so it looks like I skipped something... What do you mean - delete the "output tree" ? is the SDK part of the source tree ? How can I get the newer "checkit" ? will it work with 1.1.0 tree ? Thank you, Ehood ehood@baratz.co.il
With "deleting your output tree..." i mean that you should delete the local output directory (e.g. unxlngi5.pro or wntmsci8.pro) in your 'odk' module. If you got the same output of the check script please check in the local <output directory >/bin/odkXXX/include if you find there several directories with header files. Especailly the header files in the 'com/sun/star/uno' directory . It seems that there are files missing, e.g Any.*, Array.*, Types.*, Reference.*, ... The problem is either that there are header files missing (but then the build should break before) or that autodoc has a problem to generate these files. I am not sure if the modified script works with out problems on your source tree (maybe it checks more content) but you checkout and try the toplevel version of this script.
Hi, I looked into the directory you mentioned (it was wntmsci9.pro) and found all the files there.. BUT there was a file 'configureWindowsNT.bat' that when run asked some questions about the SDK... I think that I am missing this SDK... Is this part of the product tree ? should it be downloaded separatly ? Thank you, Ehood
The odk module build one part of the sdk. The configureWindowsNT.bat is a script to configure a SDK later. It has nothing to do with the build process, this file is packed into a SDK. You don't need a SDK during the build. If you have still the same error. Try the following command and check the ouput: move into the odk/wntmsci9.pro/bin directory, crerate a test directory 'bla' and call autodoc -html .\bla -name BLA -lg c++ -p sal .\odk645\include -t sal -t osl -t rtl -p store .\odk645\include -t store -p registry .\odk645\include -t registry -p cppu .\odk645\include -t cppu -t com -t typelib -t uno -p cppuhelper .\odk645\include -t cppuhelper -p bridges .\odk645\include -t bridges
Hi, Did what you suggested. First, I did not find autodoc in this directory, I went to oo_1.1_src\odk\wntmsci9.pro\bin and started: .\odk645\windows\bin\autodoc The message box I got was: "This application failed to start because stlport_vc6.dll was not found. Re-installing the application may fix this problem." when I stand in the above bin I see: Directory of E:\OOo\oo_1.1_src\odk\wntmsci9.pro\bin\* 31/03/2004 13:48 <DIR> . 31/03/2004 13:48 <DIR> .. 31/03/2004 13:48 <DIR> bla 31/03/2004 10:45 <DIR> odk645 31/03/2004 10:26 24,646 officebean.dll 31/03/2004 10:26 82,944 officebean.pdb Any ideas ? Ehood
You should try in your prepared build environment!!! Nothing have to reinstalled.
I am sorry - you have to be more specific... I was at my "prepared build environment" which is SRC\odk\wntmsci9.pro\bin and I send the "dir" command output and still the command you told me to run was not there. 1. Is this OK that the command was in SRC\odk\wntmsci9.pro\bin\odk645 \windows\bin\autodoc ? 2. Are am I missing any files according the "dir" command ? 3. Why is the comand fail with the message I sent you ? 4. What else should I check / do ? Thank you. I know that it is not easy to help cross the Email... but I want you to understand that I am not familier with the structure of the src tree and you must be more specific in pathes so I will understand if I am missing anything. Sorry and thanks again, Ehood Ehood
ok, with build env i mean the OO build env where you initially tried to build the odk module. In this env you should have all tools available. If not please setup a new OO build env in your shell.
Hi, OK - I got it: you ment I should run the 'winnv.bat' in my src tree. After doing so I run the command you told me and there were many lines of 'parse...' and then three lines of 'Create' with some points and it finished OK... I tried again the build and it failed with the same message !!! This is realy a strange behaviour... Any more ideas I can use ? Ehood
First thing, i have changed the prio because it is a locally problem in your env. It can't work because you have generated the docu in a directory bla, this was only for testing. You should load the ...\bla\index.html file and should navigate to the missing uno types (e.g com.sun.star.uno.Any) . Please check the output and check also if the genrate files are availbale (e.g ...bla\cpp\ref\names\com\sun\star\uno\Any directory, ...\bla\cpp\ref\names\com\sun\star\uno\c_Any.html)
Hi, 1. I think this is a general problem - as long as I followed the documents and it did not build propoerly - I think the pri should remain (unless I did something wrong locally...) 2. There was no 'cpp' directory under ...\bla and I do not understand what is: "navigate to the missing uno types (e.g com.sun.star.uno.Any)" - can you please clear this ? Thank you, Ehood
I can't reproduce your problem, the prio is right as it is. oh sorry, it was my mistake forget the cpp\ref part in the pathes. Look directly in the bla directory. You should look if anyhting was generated for the missing types mentioned earlier. Are you able to build anything, i mean do you still have build all the projects before odk?
Hi, 1. Yes - everything was build just before this ODK directory. 2. Under the bla directory I see only: [E:\OOo\oo_1.1_src\odk\wntmsci9.pro\bin\bla]dir Volume in drive E is Extra Serial number is 78D1:8EF6 Directory of E:\OOo\oo_1.1_src\odk\wntmsci9.pro\bin\bla\* 31/03/2004 15:40 <DIR> . 31/03/2004 15:40 <DIR> .. 31/03/2004 15:40 <DIR> index-files 31/03/2004 15:40 <DIR> names 31/03/2004 15:43 336,304 def-all.html 31/03/2004 15:43 8,327 help.html 31/03/2004 15:43 2,617 index.html So it looks like even the BLA directory does not contain what you thought. Waiting for an idea. Ehood
did you have checked: ...\bla\names\com\sun\star\uno\c_Any.html and did you have checked the genrated html docu (using a browser ;-)) Are you sure that in odk\wntmsci9.pro\bin\odk645\include a file odk\wntmsci9.pro\bin\odk645\include\com\sun\star\uno\Any.h|hxx exists? So if the Any.h|hxx exists but nothing was generated for this type in your bla\... directory, then the "autodoc" tool has a problem. In this case i would try to rebuld it. I have no other idea, sorry. But it would be definitely no problem in the build process of the odk module. The build error would only an aftereffect.
Hi, 1. ...\bla\names\com\sun\star\uno does not contain c_Any.html... 2. Yes, the files ...\odk\wntmsci9.pro\bin\odk645 \include\com\sun\star\uno\Any.h and Any.hxx are there... 3. How do I rebuild the 'autodoc' tool ? What should I delete there ? In which directory ? Thank you, Ehood
The bug cannot be reproduced
The Issue you raised has been marked as 'Resolved' and not updated within the last 1 year+. I am therefore setting this issue to 'Verified' as the first step towards Closing it. If you feel this is incorrect, please re-open the issue and add any comments. Many thanks, Andrew Cleaning-up and Closing old Issues ~ The Grand Bug Squash, pre v3 ~ http://marketing.openoffice.org/3.0/announcementbeta.html
As per previous posting: Verified -> Closed. A Closed Issue is a Happy Issue (TM). Regards, Andrew