Issue 22955 - build breakage: gcc vs. Microsoft C/C++ Compiler
Summary: build breakage: gcc vs. Microsoft C/C++ Compiler
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: configure (show other issues)
Version: OOo 1.1
Hardware: PC Windows 2000
: P1 (highest) Trivial (vote)
Target Milestone: OOo 1.1.1
Assignee: foskey
QA Contact: issues@tools
URL:
Keywords:
Depends on: 23345
Blocks:
  Show dependency tree
 
Reported: 2003-11-27 20:55 UTC by pavel
Modified: 2006-03-14 21:02 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description pavel 2003-11-27 20:55:32 UTC 
Ken,

your patches removing gcc2.95 support caused my build on Windows to fail:

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


Why do we check for gcc on Windows if it is not supported compiler?

Before your patches:

checking for gcc... gcc
checking for C compiler default output... 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... checked (gcc 2.95.3-5)
checking the GNU make version... checked (make 3.79.1)
checking the Microsoft C/C++ Compiler... checking for mspdb70.dll... no
checking for mspdb60.dll... /cygdrive/c/Progra~1/Micros~3/Common/MSDev98/Bin/msp
db60.dll
checking for cl.exe... /cygdrive/c/Progra~1/Micros~3/VC98/Bin/cl.exe
found.
checking the Version of Microsoft C/C++ Compiler... found Compiler version 00120
0008804.
checking how to run the C preprocessor... /cygdrive/c/Progra~1/Micros~3/VC98/Bin
/cl.exe -E
Comment 1 foskey 2003-11-28 06:54:29 UTC 
YOu must be using an old cygwin.  The compiler switched to gcc 3.3
sometime ago (months I think).  As an immediate solution you should
update your cygwin to the current release, this will "hide" the
problem in the script.
Comment 2 foskey 2003-11-28 07:03:56 UTC 
Implemented correction is --with-cl-home used to locate compiler.
Comment 3 pavel 2003-11-28 20:30:34 UTC 
With this change, running configure with
--with-cl-home=/cygdrive/c/Progra~1/Micros~3/VC98:

checking for gawk... gawk
checking for gawk... /usr/bin/gawk
checking for sed... /usr/bin/sed
checking the operating system... checked (WINNT)
checking for gcc... /cygdrive/c/Progra~1/Micros~3/VC98/bin/cl

And build is stuck here and does not continue further.
Comment 4 quetschke 2003-12-09 18:24:34 UTC 
Would you mind cc'ing me next time?

I also filed an issue on this, iz 23354 will do something tonight.
Comment 5 pavel 2003-12-09 19:14:14 UTC 
Of course - sorry I forgot that.
Comment 6 quetschke 2003-12-09 19:48:38 UTC 
Sorry, wrong issue number, use issue 23345 instead.
Comment 7 quetschke 2003-12-20 19:32:30 UTC 
This is fixed in 23345. Closing as fixed.
Comment 8 pavel 2003-12-20 22:26:42 UTC 
Verified, closing.