-29 Nov 96  15:05:24-
=Marcel Vandevusse babbled to All about GCC and ALP=

 MV> I am porting a program from linux to OS/2, using GCC to compiler the C
 MV> code, and ALP (a MASM compatible compiler from IBM for 32 bit OS/2) to
 MV> assemble the assembly. Now the problem is with global variables that
 MV> need to be seen by both. I tried to link both with ILINK and LINK386,

You're using the EMX package, right?  EMX comes with the AS and LD
programs with which you should be familiar.  With EMX, you can compile
and link your entire program from the gcc command line:

gcc -Zomf my.c my.S my.def my.rc some.obj -lmy.lib

EMX was designed to ease porting from UNIX to OS/2.  Take advantage of
its compatibilites.

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

Did you remember to put the .386P directive *BEFORE* the EXTRN
declaration?  This is required if ALP is truly MASM compatible.

Mike Phillips
INTERNET:  phil4086{at}utdallas.edu


... Better to be tried by 12 than carried by 6.
--- FMail 1.0g