X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49F5EC18.6090109@gmail.com>
Date: Mon, 27 Apr 2009 18:32:08 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Speclib problems
References: <49F5E7F4 DOT 6080909 AT cornell DOT edu>
In-Reply-To: <49F5E7F4.6080909@cornell.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Ken Brown wrote:

> I don't know anything about import libraries, but I wonder if these
> errors are caused by the speclib problems that have been discussed in
> recent weeks.

  Nope, no relation whatsoever.  The speclib stuff relates only to the system
libraries libc, libm, libdl, libutil, libcygwin, libpthread.  I think your
zlib problem comes from somehow getting both a statically-linked in-tree build
of zlib and the system's zlib dll import library into the final link at the
same time.  The undefined references in the other libs I can't guess where
they come from, you'll have to track them down - maybe the libs aren't in
dependency-order on the linker commandline.

    cheers,
      DaveK





--
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/