Minor Problem building GCC 2.3.3 on SCO systems

Thread View: gnu.gcc.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Daniel R. Guilderson Wed, 27 Jan 1993 03:14

#1663

Author: Daniel R. Guilderson
Date: Wed, 27 Jan 1993 03:14

23 lines
1522 bytes

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.

Thanks.

Daniel R. Guilderson                 Zenith Data Systems / Bull
508-294-6612                         300 Concord Road    MS 853A
drg@candidus.ma30.bull.com           Billerica, MA 01821

semper liberi

Minor Problem building GCC 2.3.3 on SCO systems

#1661

Author: Ian Lance Taylor
Date: Wed, 27 Jan 1993 03:18

24 lines
1700 bytes

   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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads