Xref: utzoo gnu.gdb.bug:574 comp.unix.i386:3654
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!think!snorkelwacker!spdcc!esegue!johnl
From: johnl@esegue.segue.boston.ma.us (John R. Levine)
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: <1990Mar21.205356.5766@esegue.segue.boston.ma.us>
Date: 21 Mar 90 20:53:56 GMT
References: <8468@pt.cs.cmu.edu> <8532@pt.cs.cmu.edu>
Reply-To: johnl@esegue.segue.boston.ma.us (John R. Levine)
Distribution: usa
Organization: Segue Software, Cambridge MA
Lines: 13

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.

asm() isn't a function, it's a compiler directive to stick in some in-line
assembler.  The standard AT&T PCC compiler and GCC understand it perfectly
well, but the MS compiler that SCO gives out doesn't.  You lose.

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.
-- 
John R. Levine, Segue Software, POB 349, Cambridge MA 02238, +1 617 864 9650
johnl@esegue.segue.boston.ma.us, {ima|lotus|spdcc}!esegue!johnl
"Now, we are all jelly doughnuts."