delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
Date: | Sun, 1 Feb 2004 10:40:43 -0700 |
From: | Sean LeBlanc <seanleblanc AT americanisp DOT net> |
To: | cygwin AT cygwin DOT com |
Subject: | Linking problems |
Message-ID: | <20040201174043.GA20082@smtp.americanisp.net> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.4.1i |
X-IsSubscribed: | yes |
Hi all. I'm currently having troubles linking against a lib. The signature it complains about certainly shows up when I search the lib. I have been able to build against other libs in the same set (MS' Host Integration Server API), but not against anything in this lib. Are there a set of things to look for when link failures like this happen? Do some windows libs get exported in different ways that require something beyond this: I'm compiling with both -L<libdir> and -l<libname>. -v doesn't seem to give me any helpful information. TIA, -- Sean LeBlanc:seanleblanc AT americanisp DOT net http://users.americanisp.net/~seanleblanc/ Get MLAC at: http://sourceforge.net/projects/mlac/ The mark of a good party is that you wake up the next morning wanting to change your name and start a new life in different city. -Vance Bourjaily, "Esquire" -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |