Apache OpenOffice (AOO) Bugzilla – Issue 23345
configure breaks with .NET2002 in some cases
Last modified: 2006-03-14 21:02:56 UTC
This is for branch cws_srx645_ooo111fix1 Configure breaks with .NET2002 if cl.exe is used before --with-mspdb-path is evaluated. This is the case for: dnl The following checks for gcc, cc and then (cl if win32) AC_PROG_CC and AC_HEADER_STDC Easy solution, but a if OS != WNT guard around them and everything is fine, or move the dnl =================================================================== dnl Check which Microsoft C/C++ or MinGW compiler is used for WINNT dnl =================================================================== part before these commands. I'll produce a patch this evening. Setting prio to 1 because build is broken for .NET2002.
Setting target to 1.1.1 Re-setting prio to P2 because if you include the path to mspdb?.dll in your PATH before calling calling configure it still builds.
Created attachment 11844 [details] Patch for configure.in
This patch should do, if approved is there a branch to committ it to?
with bash/cygwin: ./configure '--with-jdk-home=C:\jdk1.4.1_05' --with-dict=ALL --with-lang=ENUS, CZECH,SLOVAK,DAN,HUNG,SLOVENIAN,DTCH,FINN --with-asm-home=/cygdrive/c/OOo/ml --w ith-use-shell=tcsh --disable-crashdump checking the operating system... checked (WINNT) checking for gcc... gcc checking for C compiler default output file name... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking for gcc... /usr/bin/gcc checking the GNU gcc compiler version... configure: error: found version "2.95.3 -5", use version 3+ of the gcc compiler
Ahh, I see, but that is Kens "Baustelle" ;-) * Can you confirm that it works when you use --with-cl-home ? * Why don't you update your gcc package in cygwin? ;-) * I'll put a guard around Kens check for MS, non-mingw builds this evening. Volker
Hi, after ./configure '--with-jdk-home=C:\jdk1.4.1_05' --with-dict=ALL --with-lang=ENUS,CZECH,SLOVAK,DAN,HUNG,SLOVENIAN,DTCH,FINN --with-asm-home=/cygdrive/c/OOo/ml --with-use-shell=tcsh --disable-crashdump --with-cl-home=/cygdrive/c/Progra~1/Micros~3/VC98 the last line printed from configure is: checking for gcc... /cygdrive/c/Progra~1/Micros~3/VC98/bin/cl and this is everything. It didn't finished thus there is probably some issue with it too as I pointed out at http://www.openoffice.org/issues/show_bug.cgi?id=22955 BTW: this system is about 200km away from me and I do not use GCC for anything there but people working on that system use it so it is their responsibility to upgrade should they need it. I do not want to intervent in their work.
Hi Pavel, > the last line printed from configure is: > > checking for gcc... /cygdrive/c/Progra~1/Micros~3/VC98/bin/cl > > and this is everything. It didn't finished thus there is probably some issue > with it too as I pointed out at > http://www.openoffice.org/issues/show_bug.cgi?id=22955 I guess I know what's wrong, but I'm at work right now and I cannot do anything until I'm back. > BTW: this system is about 200km away from me and I do not use GCC for > anything there but people working on that system use it so it is their > responsibility to upgrade should they need it. I do not want to intervent > in their work. Ok, ok, next time I put a smilie behind such a sentence, basically it's just a bug, configure has to work for any gcc compiler when we use MS compilers. Volker
Hmm, there was a smilie ;-)
Created attachment 11884 [details] Patch for configure.in
New patch, this should also solve issue 22955. Don't forget to run autoconf to get configure regenerated.
vq->hr: As you're doing the fix1 integration, this should also go in. I tested the last version of the patch with a MSVC6-4nt configuration.
vq: I have seen the smiley too ;-) Unfortunately I'm not able to test the patch right now. Xmas will kill me soon...
I did check for Windows. vq->waratah: Ken can you test with *nix?
Approved no problem. ON thing to check is that the test for GCC=YES does not need the extra clutter, I think if you avoid the compiler checking then GCC will != YES
vq->waratah: I guess you're right, AC_PROG_CC sets the GCC variable. I'll change the "clutter" into a comment once I commit it into ...fix2.
reassigned to vq as he takes action on it, please mark as fixed once committed to fix2
This makes the build not possible with fix2: ./configure '--with-jdk-home=C:\jdk1.4.1_05' --with-dict=ALL --with-lang=ENUS,CZECH,SLOVAK,DAN,HUNG,SLOVENIAN,DTCH,FINN --with-asm-home=/cygdrive/c/OOo/ml --with-use-shell=tcsh --disable-crashdump --with-cl-home=/cygdrive/c/Progra~1/Micros~3/VC98 is stucked at checking for gcc... /cygdrive/c/Progra~1/Micros~3/VC98/bin/cl and does not continue... raising prio to P1.
> is stucked at > > checking for gcc... /cygdrive/c/Progra~1/Micros~3/VC98/bin/cl This output belongs AC_PROG_CC , but this is now guarded with if test "$_os" != "WINNT" -o "$WITH_MINGWIN" = "yes"; then AC_PROG_CC fi so if you don't have WITH_MINGWIN set this test isn't executed for WINNT. I guess you didn't regenerate your configure. I just committed configure.in and configure to cws_fix645_ooo111fix2. Resolving fixed. You used: > ./configure '--with-jdk-home=C:\jdk1.4.1_05' --with-dict=ALL -------------------------------^^^ Does that really work? > --with-lang=ENUS,CZECH,SLOVAK,DAN,HUNG,SLOVENIAN,DTCH,FINN > --with-asm-home=/cygdrive/c/OOo/ml --with-use-shell=tcsh --disable-crashdump > --with-cl-home=/cygdrive/c/Progra~1/Micros~3/VC98
verified - thanks. BTW - --with-jdk-home=C:\jdk1.4.1_05 is a remnant from migration. Of course it does not work ;-)
I try to update the config_office directory by tortoise cvs today. I try again without this patch, but I got error. when I applied this patch everything is OK. so maybe this patch is not yet included in fix2 ? or I wrongly update ? Thanks
Hi utomo, I never used tortoise cvs, but make sure that you really use the branch cws_fix645_ooo111fix2 . I just checked, the changes are in that branch.