Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com To: cygwin AT cygwin DOT com Subject: Re: can't link fortran executable References: <80575AFA5F0DD31197CE00805F650D7602D05A AT wilber DOT adroit DOT com> From: Andrey Khavryuchenko Organization: KDS Software Group X-Attribution: AVK Content-Type: text/plain; charset=US-ASCII Date: 05 Nov 2001 19:39:51 +0200 In-Reply-To: <80575AFA5F0DD31197CE00805F650D7602D05A@wilber.adroit.com> Message-ID: Lines: 19 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 David, "RD" == Robinow, David wrote: RD> You are using g77 as a linker. Are you also using it as a compiler? RD> If not, where did your object files come from? [This looks RD> suspiciously like 'f2c' output, which requires -lf2c on the link RD> command.] Every .o was built using g77. Linking I'm also via g77, as it's shown in the command line. Just noticed. Strange, but if I build using $ g77 -o chngc.exe *.f everything goes ok. -- Andrey V Khavryuchenko http://www.kds.com.ua/ Offshore Software Development -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/