Article View: comp.os.os2.programmer
Article #483Re: link386, why not ld?
From: Barr3y Jaspan
Date: Sun, 26 Jul 1992 17:45
Date: Sun, 26 Jul 1992 17:45
17 lines
1243 bytes
1243 bytes
In article <dave.711311333@stat.tamu.edu>, dave@stat.tamu.edu (Dave Perry) writes: |> Just curious, why is it that we use link386, rather than ld for |> linking regular old C programs in os/2? Why does it strike you as odd that you have to use the OS/2 linker under OS/2, instead of using the Unix linker under OS/2? gcc produces OS/2 .obj files, and ld does not understand them. (emx/gcc uses a different approach in which it embeds Unix .o information in the .obj file.) |> Also, the programs that |> I have tried will not print anything out until they are finished |> running! See the answer to this question in the OS/2 Programmer's FAQ. -- Barr3y Jaspan, bjaspan@mit.edu
Technical Details
Message-ID:
<1992Jul26.174539.13668@athena.mit.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!van-bc!rsoft!agate!ames!sun-barr!cs.utexas.edu!usc!sdd.hp.com!swrinde!gatech!bloom-beacon!bloom-picayune.mit.edu!athena.mit.edu!bjaspanReferences:
<dave.711311333@stat.tamu.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!van-bc!rsoft!agate!ames!sun-barr!cs.utexas.edu!usc!sdd.hp.com!swrinde!gatech!bloom-beacon!bloom-picayune.mit.edu!athena.mit.edu!bjaspan From: bjaspan@athena.mit.edu (Barr3y Jaspan) Newsgroups: comp.os.os2.programmer Subject: Re: link386, why not ld? Message-ID: <1992Jul26.174539.13668@athena.mit.edu> Date: 26 Jul 92 17:45:39 GMT References: <dave.711311333@stat.tamu.edu> Sender: news@athena.mit.edu (News system) Organization: Massachusetts Institute of Technology Lines: 17 Nntp-Posting-Host: hodge.mit.edu