Hello Udo!

13 Aug 96 19:14, Udo Van Den Heuvel wrote to All:

 UVDH> e:\prg\watcom\lib386\os2\clib3r.lib(inirt386) :  warning L4005:
 UVDH> 32-bit fix-up in 16-bit record ignored at 5B in segment

 UVDH> How can I avoid the warnings of LINK386?

Use wlink instead.  Watcom does automatic 16-bit thunking; CSet/2 requires
explicit 16-bit thunking.

 UVDH> In what library is '_end' to be found?

No idea.  The only presence I know of such a variable, is in the resource
compiler, not Watcom.

 UVDH> When I use WLINK everything links OK, except for the
 UVDH> testudo{at}importpath thingie.

Exactly my point.

 UVDH> === Cut Begin: testudo.pas ===
 UVDH> Program TestUdo;

 UVDH> Procedure importpath (Var local,canon,remote:String); external;
 UVDH> {$L e:\tmp\udo\import.OBJ}

 UVDH> Var test1,test2,test3:String;

 UVDH> Begin
 UVDH>        importpath(test1,test2,test3);
 UVDH>        WriteLn(Test1);
 UVDH> End.
 UVDH> === Cut End ===

 UVDH> How can I fix the 'testUdo{at}importpath' problem (unresolved
 UVDH> external)? PLEASE help!

Well, it appears that's the way Speed/2 writes the function name to the object
file.  Because you're linking it in with C, make sure that your C program
declares the function as:

extern _pascal importpath( char *local, char *canon, char *remote ) ;

As for the 'testUdo{at}' portion, I have no idea why that's getting in there, as I
don't use pascal.

Daniel

Internet:  dbl{at}eznet.ca

... I accept your apology, {at}FN{at}, but not your explanation.

--- GoldED/2 2.42.G0615+