Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!prism!loligo!geomag!prem
From: prem@geomag.fsu.edu (Prem Subramanyan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Blink error msg: undefined symbol
Keywords: blink
Message-ID: <168@loligo.cc.fsu.edu>
Date: 26 Jun 89 14:31:33 GMT
References: <7760@hoptoad.uucp>
Sender: news@loligo.cc.fsu.edu
Reply-To: prem@geomag.UUCP (Prem Subramanyan)
Distribution: usa
Organization: Florida State University Computing Center
Lines: 24


       Ah, good ol' blink.  I have recently run into problems with it myself.
       after careful search through the documentation, I discovered in very
       fine print, the necessary correction.  I doubt that the problem is in
       your code, but in the linkage.  _stub is the name that blink wants to
       give to every function that is not defined, allowing development of
       code sans functions and then adding in the functions later.  What you
       need to do is blink the following way.
	
	blink from lib:c.o,{other files} to {executable} lib {libraries}
       
       the important part to include is the lib:c.o at the beginning of the
       link.  Heck, I had problems with lc.lib until I added the c.o part at
       the beginning.  After adding c.o, the files linked correctly.  For a
       while, blink really had me going.  I followed its advice and re-compiled
       all of my modules with the option -b0, which took incredibly long as my
       machine only has 512K, forcing me to put quad files to disk.  So, after
       several hours of compiling and re-compiling, I looked again at the linking
       docs in the compiler usage section of the manual (not the command section
       as the docs on blink did not tell me about c.o there) and found this solution.

       I hope this will be of help--Happy Compiling.....

       --- Prem Subrahmanyam