🚀 go-pugleaf

In article <1993Mar4.044754.17560@math.ucla.edu> nzhong@oak.math.ucla.edu (Ning Zhong) writes:
>  I downloaded the GCC v.2.2.2 from ftp-os2.nmsu.edu (directory /pub/os2/2.0/
>programming/gcc2-2.2.2) and installed in my D: drive like this:
...
>and I did add these to my config.sys following the documentation , but 
>when I tried to compile the sample1.c ("hello world" sample program), I typed:
>    gcc -v sample1.c
>the output goes:  
>    cpp -lang-c -v -undef [bla bla bla] sample1.c D:/GCC/TMP/cc000008.i
>    cc1 D:/GCC/TMP/cc000008.i -quiet [bla bla bla] -o D:/GCC/TMP/cc000008.s
>    as  -o D:/GCC/TMP/cc000008.o D:/GCC/TMP/cc000008.s
>    o2obj D:/GCC/TMP/cc000008.o -o 000008.obj
>    ld  D:/GCC/TMP/cc000008.obj -lgcc -lc -lgcc
...
>I did try "gcc -c sample1.c" and then "link386 sample1.obj" though, and it 
>worked. I just want to know whether this can be done in a single command, 
>and using the GCC linker, if there is one. And a final question, what "-l"
>option should I use to compile a C++ program?

You should do this.  The normal procedure for GCC/2 (I don't know
about EMX/GCC - anyway, this looks symptomatic of GCC/2) is:

gcc -c filename.c
link386 filename.obj, filename.exe,,os2.lib,filename.def;

Note that a .def file is required if you write PM code, and is useful
even if you don't.  Most books on OS/2 programming (and the LINK386
documentation in the IBM toolkit/2) explain .def files.

ld is a Unix linker that accepts *.o files and *.a files instead of
*.obj and *.lib files.  It is not included with GCC/2, since it
couldn't link to IBM's .lib files anyway.  GCC produces .o files and
runs o2obj in order to produce .obj files from them.

Because of this, GCC/2 does not link, although a rexx script (ld.cmd)
could be written to accept the ld commands and run link386 with the
proper commands.

C++ code will require a collect step.  Use collect.exe to do this.  I
don't know exactly how, though.  I have not written any C++ code with
GCC.
-- 
David Charlap                 dic5340@hertz.njit.edu
begin 666 signature.txt
B22!C86XG="!B96QI979E('EO=2!D96-O9&5D('1H:7,A"@