Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!hellgate.utah.edu!caen!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!ncar!gatech!ncsuvx!news
From: johnson@ecovsh.eco.ncsu.edu (Amy Johnson)
Newsgroups: comp.unix.aix
Subject: Re: Problem when linking fairly large FORTRAN object files
Keywords: AIX3.1, RISC6000, link, FORTRAN
Message-ID: <1990Nov16.155733.12813@ncsuvx.ncsu.edu>
Date: 16 Nov 90 15:57:33 GMT
References: <11256@ccncsu.ColoState.EDU>
Sender: news@ncsuvx.ncsu.edu (USENET News System)
Reply-To: johnson@ecovsh.eco.ncsu.edu
Organization: North Carolina State University
Lines: 33

In article <11256@ccncsu.ColoState.EDU>, flatau@handel.CS.ColoState.Edu
(flatau) writes:
|>I am having problems linking (fairly large, 30K lines) FORTRAN program
|>on RISC6000/320 AIX3.1 + 3002 (September) update, 16Mb:
|>
|>
|>I have a library, say "rams.a"  made with "ar r" command.
|>This library contains about 10  modules (approx 1000 lines each),
|>and each module contains several FORTRAN subroutines (i.e. I am
|>NOT fsplitting them).
|>
|>Next, I am linking several *.o files with
|>
|>xlf -o ramsexe  *.o rams.a
|>
|>this results in unsatisfied external refs, even though, I am
|>certain these externals are in the library. I have traced the 
|>problem a bit further: seems like removing one particular
|>object file from *.o list makes the problem to go away.
|>However, this particular object file is not unusual in any way.
|>

I got bit by this problem myself a couple weeks ago.  Try using the flag:

	-b nodelcsect

on the link line.  It worked for me.

Amy <johnson@ecovsh.eco.ncsu.edu>
Engineering Computer Operations
North Carolina State University