Article View: comp.os.os2.programmer
Article #754Re: OS2 Device Driver in C -- Linking Problem
From: dave
Date: Sat, 05 Sep 1992 13:56
Date: Sat, 05 Sep 1992 13:56
21 lines
1533 bytes
1533 bytes
In <1992Sep3.222735.22713@hns.com> Pat O'Neil writes:
> The C/2 manual says that the linker
> locates segments in the order it encounters them. This seems
> true until I start bringing in the C run-time libraries
> (which I need for sprintf, strtok, memcpy, etc.). If I link
> without the library (and thereby get a zillion unresolveds)
> the map at least says that the data segment is first.
I believe that there is a record in the library which tells the linker
to do DOSSEG segment ordering. If there is no /NODOSSEG linker
directive, then I think you'll have to hack the library and remove this
record. I recall hearing about highly bizarre behaviour when the MSC
runtime gets linked in non-DOSSEG order, but I can't for the life of me
recall exactly what it was that happened. But caveat emptor.
dave
-------------------------------------------------------------------------
Dave Mooney dmm@vnet.ibm.com
C Set/2 Development, IBM Canada Lab, 844 Don Mills Rd, Toronto, Ontario
"If you've got a blacklist, I want to be on it"
Technical Details
Message-ID:
<19920905.065556.673@almaden.ibm.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.comReferences:
<1992Sep3.222735.22713@hns.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!vnet.ibm.com From: dmm@vnet.ibm.com (dave) Message-ID: <19920905.065556.673@almaden.ibm.com> Date: Sat, 5 Sep 92 09:56:04 EDT Newsgroups: comp.os.os2.programmer Subject: Re: OS2 Device Driver in C -- Linking Problem Organization: IBM Canada Lab News-Software: UReply 3.0 X-X-From: dmm@vnet.ibm.com (Dave Mooney) References: <1992Sep3.222735.22713@hns.com> Lines: 21