Apache OpenOffice (AOO) Bugzilla – Issue 16084
W32 build with .NET fails in python
Last modified: 2003-07-31 09:22:15 UTC
The build breaks because Python-2.2.2/Modules/_hotspot.c needs largeint.h and Python-2.2.2/PC/python_nt.rc needs ver.h These files are in the standard include directory from MSVC6, but microsoft obviously skipped them for .NET . After copying the files from VC6 to some solver/../inc the module builds. Ideas? (Yes, at least for ver.h. patch python_nt.rc to use winver.h)
Hmm, we should get this solved until 1.1, lets try 1.1RC
Hi, I don't yet have a .net compiler yet, the .net port was actually done by obo@openoffice.org, maybe he can say something about this. ( Note, that some .NET port changes are not yet part of the ooo11rc, I don't know, whether this is by desired or not). Bye, Joerg
Do you really use Python-2.2.2.patch rev. 1.4 ? In this patch the fix is already included. Oliver.
No, at the moment cws_srx644_ooo11rc still uses rev1.1. vq->mh: Can we merge rev 1.4?
Additionally needed files: convert.sh (rev. 1.1), convert.bat (rev 1.1), makfile.mk (rev. 1.4) these are necessary to prevent the damage of UNIX builds. Oliver.
.
Sorry to reopen, but now we're in merging hell! If we use rev 1.4 of makefile.mk, the first patch to it on RC (1.3 -> 1.3.2.1) is already merged, but the second (1.3.2.1 -> 1.3.2.2) is not and will conflict. vq->pjanik: Can you please check out (from HEAD): makefile.mk rev. 1.4 Python-2.2.2.patch rev. 1.4 convert.sh rev. 1.1 convert.bat rev. 1.1 and test if the parallel build works with this revisions from HEAD.
Reassigned to Pavel, please test!
It works on GNU/Linux system - both python and pyuno compiled. Can we close it Joerg? I did not track this issue and reading about .NET is not my preferred reading for the night :-))
Sorry Pavel, did you read the previous post in this issue? > vq->pjanik: Can you please check out (from HEAD): > > makefile.mk rev. 1.4 > Python-2.2.2.patch rev. 1.4 > convert.sh rev. 1.1 > convert.bat rev. 1.1 > > and test if the parallel build works with this revisions from HEAD. Sorry for the .NET stuff. OK to use the HEAD versions? Volker
No, as I said, I have not read it completely - I will look at it tomorrow because I have yet to finished non-SMP build of current CVS.
In order to get this build correctly in msdev6,cygwin-tcsh, MAXPROCESS=4 I need the following patch to makefile.mk . With msdev6,4nt shell, I can't build, I get something like [z:\oo1.1beta2\python]dmake cc: Command not found. /usr/bin/sed: -e expression #1, char 17: Unterminated address regex dmake: Error code 1, while making 'Shell escape' without the faintest idea, where this comes from.
Created attachment 7316 [details] patch for msdev6/ cygwin tcsh build
Hi Joerg, > In order to get this build correctly in > > msdev6,cygwin-tcsh, MAXPROCESS=4 > > I need the following patch to makefile.mk . Looks reasonable. > With msdev6,4nt shell, I can't build, I get something like > ... > cc: Command not found. > /usr/bin/sed: -e expression #1, char 17: Unterminated address regex > dmake: Error code 1, while making 'Shell escape' > > without the faintest idea, where this comes from. Five minutes ago I run into a similar problem. ;-) Your current dmake is the cygwin version. You have to delete dmake/dmake.exe and solenv/wntmsci9/bin/dmake.exe, clear the dmake directory and build a new dmake with winenv.bat. Another possible problem: When you generate your winenv.bat, you get also a winenv.set !!!! This can not be used to build with W32-tcsh, you have to create a correct winenv.set with $ configure --with-use-shell=tcsh ... Volker
BWMHOTT (Banging with my head on the table) :) So, I think with the patch, everything should be fine. Thx, Joerg
Will you commit the changes? (All four files?)
Sorry, didn't mention, that I don't have write access in external (just udk, dba, and installation). So will you (vq) commit ?
I committed the patch to cws_srx645_ooo11rc2. The cws_srx645_ooo11rc branch still doesn't contain the changes and will not build with .NET. Just use the rc2 version instead.
Resolving issue, patch is in rc2 and rc3.
closing fixed issues for 1.1. release.