Xref: utzoo comp.lang.c:38599 comp.unix.sysv386:7205
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!bu.edu!m2c!applix!scotte
From: scotte@applix.com (Scott Evernden)
Newsgroups: comp.lang.c,comp.unix.sysv386
Subject: Re: Another GCC 1.39 and Sys Vr4 problem.
Keywords: gcc, SysVr4
Message-ID: <1187@applix.com>
Date: 23 Apr 91 05:47:38 GMT
References: <1991Apr22.005126.425@swsrv1.cirr.com>
Reply-To: scotte@applix.UUCP (Scott Evernden)
Organization: APPLiX Inc., WestboroMA
Lines: 18

In article <1991Apr22.005126.425@swsrv1.cirr.com> toma@swsrv1.cirr.com (Tom Armistead) writes:
>Thanks to the replies about hot to fix the messed up header files for Sys Vr4
>so that GCC doesn't barf on them.  The solution was the fixinclude script
>that comes with GCC 1.39.
>
>Now for the next problem: This is on Unix System Vr4
>
>I have gcc compiled just fine and it will produce executable files just fine,
>but if I use the -g command line option, I get an error from cc1 saying that
>'-g' is an invalid option - Here's an example of the error?

I don't yet have 1.39 but do have a 1.37.1 hacked for SVr4.  I couldn't
make the -g option work because the compiler apparently does not emit 
assembler debugger directives in the format expected by as.

I would suspect that this capability was "tied off" in 1.39, maybe?

-scott