Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!cs.utexas.edu!uunet!comcon!leif
From: leif@comcon.UUCP (Leif Sawyer )
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C Linking Problem
Summary: Turbo C link problems Fixed with a response file.
Message-ID: <267@comcon.UUCP>
Date: 23 Jan 90 11:13:04 GMT
References: <1997@uwm.edu> <25BAB7FC.13768@maccs.dcss.mcmaster.ca>
Distribution: usa
Organization: Computer Connection - Anchorage, Alaska
Lines: 58

In article <25BAB7FC.13768@maccs.dcss.mcmaster.ca>, cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) writes:
> In article <1997@uwm.edu> peter@csd4.csd.uwm.edu (Peter J Diaz de Leon) writes:
> $	I am trying to link several object moduals that were
> $	compiled in Turbo C 2.0 using tlink. However, I keep 
> $	getting the error
> $		Fatal:Comman arguments too long
> $	How do I get around this?  A copy of the tlink line
> 
>    Use a response file.  For details of how to do this, check out the
> documentation that came with your copy of Turbo C.  I've never used
> this feature of the linker, so I don't know offhand how to do it.
> 

Using a response file is pretty simple. For the first few time you do it, 
it may be simpler to modify a 'quicky'.  
From dos:
c:\turboc\source> tcc dummy.c
  tcc.......
  compiling...
  linking...
c:\turboc\source> del dummy.obj
c:\turboc\source> del dummy.exe
c:\turboc\source> qu turboc.$ln

this is a temp file used by tcc to call tlink.
here's an example one:
d:\turboc\source> type turboc.$ln

d:\turboc\lib\c0m.obj+
mcvert+
hqxify+
unpack
mcvert
/c/v/x
d:\turboc\lib\EMU.LIB+
d:\turboc\lib\mathm.lib+
d:\turboc\lib\cm.lib

d:\turboc\source>

as you can see, the first line is the startup module, c0x, where x is the
code model. next is the list of .OBJ files to be linked together. multiple
files are concatenated by the use of a '+' (plus) sign at the end of the 
filename. a filename with no '+' denotes the last .OBJ file to be included.
Next is the .EXE filename. After that is the line containing any options
that have been passed to the linker-defaulting to /x(ecutible file), /v(debug),
/c(ase significant).  After the option line is a list of library files to 
include, starting with any user-defined libraries, then the defaults.
The same rule of multiple files applies to the .LIB files as to the .OBJ files.


Hope this helps out some!
 
-- 
:- From Leif Sawyer  ----  USnail -= 1568 Primrose/Anch/AK/99508-3062        -:
:- UUCP - uunet!comcon!leif1       "Does the name Pavlov ring a bell? "      -:
:- BitNet - ASLAS@Alaska.BitNet                 #define flame /dev/null      -:
:-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-: