I am porting a program from linux to OS/2, using GCC to compiler the C
code, and ALP (a MASM compatible compiler from IBM for 32 bit OS/2) to
assemble the assembly. Now the problem is with global variables that need
to be seen by both. I tried to link both with ILINK and LINK386, with the
same results. Example: one of the variables is calles PARG (_PARG in the
assembly code).

In the C code:

unsigned long PARG=0;

in the C .h file:

extern long PARG;

and in the assembly file:

EXTRN _PARG:DWORD

The C code can use this variable no problem, and when looking at the code
through IPDM, it is referenced as address 0x0002 0040. As soon as the
assembly language part tries to access the variable (even just trying to
read it) I get an access violation. The problem is that IT is trying to
access the variable as 0x0000 0040.

Is this a quirk with ALP, a problem with GCC, a linker bug, or an error on
my part? This is the first time I'm trying to link an executable from
object files created by more than one program (be it a compiler or an
assembler).



--- Maximus/2 3.01