home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ferkel.ucsb.edu!taco!rock!stanford.edu!agate!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!cis.ohio-state.edu!cygnus.com!ian
- From: ian@cygnus.com (Ian Lance Taylor)
- Newsgroups: gnu.gcc.bug
- Subject: Minor Problem building GCC 2.3.3 on SCO systems
- Date: 26 Jan 1993 22:18:13 -0500
- Organization: GNUs Not Usenet
- Lines: 25
- Sender: daemon@cis.ohio-state.edu
- Approved: bug-gcc@prep.ai.mit.edu
- Distribution: gnu
- Message-ID: <9301262006.AA03674@tweedledumb.cygnus.com>
- References: <9301261825.AA23121@candidus.ma30.bull.com>
-
- Date: Tue, 26 Jan 93 13:25:28 -0500
- From: drg@candidus.ma30.bull.com (Daniel R. Guilderson)
-
- I just recently retrieved the gcc-2.3.2-2.3.3 patch. In case you have
- forgotten I am the guy who had some problems building gcc-2.3.2 on SCO
- UNIX 3.2v4. The new patch is great. I have only one minor problem to
- report. The default CFLAGS for the bootstrap compile contains a '-g'
- to enable debugging. This caused the Microsoft C compiler to become
- confused. It somehow thought it was compiling Xenix code and
- apparently tried to convert OMF files. Here is an example of the
- output.
-
- cc -nointl -DIN_GCC -D__STDC__=0 -g -I. -I. -I./config -c ./cexp.c
- ./cexp.c
- /usr/bin/.cvtomf: fatal error -- No input file specified
-
- I solved the problem by redefining CFLAGS so that the '-g' flag was
- turned off during the bootstrap.
-
- I don't understand why this happened. I just tried it again, and it
- didn't happen to me. I don't even have a program /usr/bin/.cvtomf.
- Does this mean that you can never run ``cc -g''? That seems peculiar.
-
- Ian Taylor
-
-