Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MS LINK- fixup error

4 views
Skip to first unread message

t.rosenfeld

unread,
Nov 4, 1986, 10:37:54 AM11/4/86
to
I'm having a terrible problem linking my program! I am using Microsoft
C and Assembler. I am trying to link in an assembly module with my C modules
and I keep getting "Fixup overflow ..." errors when I link. After much barking
up the wrong tree I had the compiler generate the .ASM via the "-Fa" option,
then assemble the .ASM file with MASM then link-- and I still got the same
error. Mind you If I did not use "-Fa" and compiled and linked in one step
I got no link errors. I am thinking that the compiler passes some secret
options to the assembler that I don't know about to make things work. The
options I used were:

masm /MX /ML

I also added the "/A",but that didn't help either. My compile command line
is:
cl -Alfu -K -Od

Any suggestions???

--
----------------
Thomas Rosenfeld
@ AT&T Information Systems Labs, Middletown, NJ
(201) 957-5867

UUCP: {harpo,ihnp4,burl,akgua}!mtgzz!rosen

Disclaimer: I don't claim anything.

Peter Ashwood-Smith

unread,
Nov 7, 1986, 9:35:29 AM11/7/86
to
> I'm having a terrible problem linking my program! I am using Microsoft
> C and Assembler. I am trying to link in an assembly module with my C modules
> and I keep getting "Fixup overflow ..." errors when I link. After much barking

What does your assembly language routines look like. Since you are
compiling for a large model, you must declare all subroutines as far not
near and handle all pointers as segement/offset pairs.

Peter Ashwood-Smith
University of Toronto.

John Allen

unread,
Nov 9, 1986, 12:04:57 AM11/9/86
to
In article <22...@mtgzz.UUCP> ro...@mtgzz.UUCP (t.rosenfeld) writes:
>I'm having a terrible problem linking my program! I am using Microsoft
>C and Assembler. I am trying to link in an assembly module with my C modules
>and I keep getting "Fixup overflow ..." errors when I link. After much barking
[etc.]

I have seen this error message a number of times, and unless I'm mistaken,
in each case the problem was a conflict between global symbols, one each in
code and data segments. My personal favorite was a global variable called
"exit".

Hope this helps,

John Allen
=========================================================================
NetExpress Communications, Inc. seismo!{sundc|hadron}!netxcom!jallen
1953 Gallows Road, Suite 300 (703) 749-2238
Vienna, Va., 22180
=========================================================================

0 new messages