Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!cs.umn.edu!wytten
From: wytten@cs.umn.edu (Dale Wyttenbach)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: linking with Borland-C 2.0
Message-ID: <1991Apr8.141017.12326@cs.umn.edu>
Date: 8 Apr 91 14:10:17 GMT
Article-I.D.: cs.1991Apr8.141017.12326
References: <1991Apr3.163007.4958@cs.umn.edu>
Organization: University of Minnesota, Minneapolis, CSci dept.
Lines: 35

I posted two questions about linking with Borland-C2.0 last week,
and I'd like to thank the many helpful people who responded.  Answers
to both my questions could be found in the Borland-C User's Guide.
One of these days I'm going to have to invent a book index that is
indexed by what you're thinking about instead of being indexed by
keywords you don't know yet :-)

In <1991Apr3.163007.4958@cs.umn.edu> wytten@cs.umn.edu (myself) writes:
>I'm trying to compile a program originally written for MSC under BorlandC.
>There are approximately 50 object files, which I have compiled with
>bcc.  I have two questions that are related.
>(1)
>When I try to link them, I get the error message:
>undefined symbol _main in module c0.asm

User's Guide, pg. 63: Options|Compiler|Code Generation|Generate Underbars
If you are linking with standard libraries, this box must be checked.

Comment: Argh!  What a ridiculous trap to set for an unsuspecting UNIX
programmer.  I used whatever the default options were, which apparently
included the standard libraries but *NOT* having this box checked.

>(2)
>When I try to link from a makefile with tlink,
>it bombs because the command-line arguments are too long.

See User's Guide, pg. 235: Using Response Files.

Thanks again!

dale
-- 
 Dale Wyttenbach     | We all shine on,
 wytten@cs.umn.edu   | like the moon, the stars and the sun.
                     |                                      --John Lennon