Thank you to Gavin Scott and Mark Bixby for their replies. Changing the case
did the trick. In my own defense (I hate to seem stupid for no reason) the
example C code from the TurboImage manual had all the intrinsics in upper
case ie. #pragma intrinsic DBOPEN. Maybe that is because the example
expected to be compiled with something that knows more about what a DBOPEN
is. Does this mean that if I'm using gcc that the intrinsic statement
doesn't really do anything?

Thanks again for your help, and for saving me from a night of banging my
head against the wall.

Tony White

-----Original Message-----
From: Mark Bixby [mailto:[log in to unmask]]
Sent: Monday, May 01, 2000 5:57 PM
To: Tony White
Subject: Re: gcc and TurboImage


Hi Tony,

Function names in C are case sensistive and are not upshifted or downshifted
by
the compiler.

The way you write a function name is the exact way the compiler compiles it.

My guess is that you used the wrong case.  IIRC, all the TurboImage stuff
lives
in XL.PUB.SYS, so you don't need to do any special linking because
XL.PUB.SYS
is *always* one of the default libraries.

- Mark B.

Tony White wrote:
>
> OK, I've searched the HP3000-L archive and I was sure that someone had
> already asked this question, but to no avail. I'm sure that I am just
being
> stupid, but perhaps someone can save me.
> What library do I need to link against to resolve the TurboImage
intrinsics?
> My code compiles and links (ha, ha), but at run time I get unresolved
> externals for all the DB-intrinsics. I've tried a lot of libraries but
none
> seem to do the trick. Am I missing something or is my system missing
> something?
>
> Please help,
>
> Tony White