Xref: utzoo gnu.gdb.bug:575 comp.unix.i386:3692
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!sco!seanf
From: seanf@sco.COM (Sean Fagan)
Newsgroups: gnu.gdb.bug,comp.unix.i386
Subject: Re: GDB on SCO Unix SysV v3.2 ?
Keywords: gdb,sco,unix,sysv,sys5,v3.2,readline
Message-ID: <5345@scolex.sco.COM>
Date: 23 Mar 90 13:24:54 GMT
References: <8468@pt.cs.cmu.edu> <8532@pt.cs.cmu.edu> <1990Mar21.205356.5766@esegue.segue.boston.ma.us>
Sender: news@sco.COM
Reply-To: seanf@sco.COM (Sean Fagan)
Distribution: usa
Organization: The Santa Cruz Operation, Inc.
Lines: 25


In article <1990Mar21.205356.5766@esegue.segue.boston.ma.us> johnl@esegue.segue.boston.ma.us (John R. Levine) writes:
>In article <8532@pt.cs.cmu.edu> libove@ius3.ius.cs.cmu.edu (Jay Libove) writes:
>>at load time for 'gdb',{the function "asm" is undefined.
>You can probably build gcc and build gdb with that.  I know someone who did
>roughly that, though the gcc build happened on 386/ix.

I've built gdb with the MSC compiler (under SCO UNIX, of course 8-)), and
don't really remember this.  Well, I take that back:  I now have a vague
recollection of it, and I may have just used rcc (which is the AT&T
compiler) to compile the one module that had the asm's.  (I also didn't
think that gcc would take the syntax that dep.c uses, but maybe I'm wrong.)
Anyway, if you choose to go that route, you may need to use the following
flags when compiling any module with rcc: -DM_UNIX -DM_XENIX -DM_I386
-DM_COFF.  I think that will take care of it.

Oh, yeah:  you also won't be able to debug gdb with gdb, if you build it
with gcc.  It gets the debugging information very wrong.

-- 

-----------------+
Sean Eric Fagan  | "Time has little to do with infinity and jelly donuts."
seanf@sco.COM    |    -- Thomas Magnum (Tom Selleck), _Magnum, P.I._
(408) 458-1422   | Any opinions expressed are my own, not my employers'.