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 Delivered-To: mailing list cygwin AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: cannot link with libtiff MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Sat, 9 Mar 2002 08:26:40 +1100 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: cannot link with libtiff Thread-Index: AcHG5Y+B5T+TLeyAT72QPdjT2ZyyEwAAkJyg From: "Robert Collins" To: =?iso-8859-1?Q?Michaela_und_Daniel_Wei=DF?= , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g28LRgX27719 > -----Original Message----- > From: Michaela und Daniel Weiß [mailto:M_D DOT Weiss AT t-online DOT de] > Sent: Saturday, March 09, 2002 8:06 AM > To: cygwin AT cygwin DOT com > Subject: cannot link with libtiff > > > Hi, > > I haven't found this problem in the mailing list archive: > > I have been trying to use libtiff (tiff-3.5.7-1) in my > program (using daily updated cygwin version). According to > the announcement (Charles Wilson on Feb 10th): > > > Now uses the auto-import functionality of newer binutils, and > doesn't use __declspec(dllimport). This means you no longer > need "-DTIFF_STATIC -DJPEG_STATIC -DZLIB_STATIC" or even > -DALL_STATIC when compiling objects intended for static > linking. Just compile as normal. (...) NO special flags at > compile-time nor link-time when linking to dynamic links. > > So I have tried to compile my program with the line: > > gcc -Wall -O3 *.c > Auto import doesn't remove the need to list the library. libm works because it's part of libcygwin which is listed in the cygwin gcc specs file. Try gcc -Wall -O3 *c -ltiff Rob -- 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/