Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.0.1.1.0.20040113215207.037d9758@127.0.0.1> X-Sender: Date: Tue, 13 Jan 2004 21:57:36 -0500 To: Mark Hadfield , Cygwin Mailing List From: Larry Hall Subject: Re: Building nco: changes in Cygwin break linking In-Reply-To: <4004868A.9030906@niwa.co.nz> References: <4004868A DOT 9030906 AT niwa DOT co DOT nz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 07:00 PM 1/13/2004, Mark Hadfield you wrote: >Hello all > >I am trying to build NCO version 2.8.0 from source (http://nco.sourceforge.net/). I have Windows 2000 SP4 with an up-to-date, reasonably complete Cygwin environment (cygwin 1.5.5-1, gcc 3.3.1-3, etc). I use the usual "./configure, make" process. The build fails to produce executables, with output like this > >/bin/bash ../../libtool --mode=link cc -g -O2 -ansi -L/usr/local/lib >-o ncwa.exe ncwa.o libnco.la -lnco -lintl -lm -lC -lnetcdf >cc -g -O2 -ansi -o ncwa.exe ncwa.o -L/usr/local/lib ./.libs/libnco.a -L/usr/lib /usr/local/lib/libnco.a /usr/lib/libintl.dll.a /usr/lib/libiconv.dll.a -lC -lnetcdf >fu000001.o(.idata$3+0xc): undefined reference to `_libc_iname' >fu000002.o(.idata$3+0xc): undefined reference to `_libc_iname' >fu000003.o(.idata$3+0xc): undefined reference to `_libc_iname' >fu000004.o(.idata$3+0xc): undefined reference to `_libc_iname' >fu000005.o(.idata$3+0xc): undefined reference to `_libc_iname' >fu000006.o(.idata$3+0xc): more undefined references to `_libc_iname' follow >Info: resolving _optarg by linking to __imp__optarg (auto-import) >Info: resolving _optind by linking to __imp__optind (auto-import) >collect2: ld returned 1 exit status > >When I followed exactly the same steps with exactly the same source on 14 Aug 2003 I did not encounter this error. IIRC, I had an up-to-date, reasonably complete Cygwin environment then. So I presume that the problem is caused by the installation of a newer version of some Cygwin software component in the meantime. > >Any suggestions on how to diagnose & solve the problem? Well, if it worked before but doesn't now, something has certainly changed. However, presumptions beyond that aren't too helpful. I'd suggest figuring out who's looking for this symbol and where it should come from. Track it from there until you find the library you're missing. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/