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 Message-ID: <00b301c1f5bb$72dc1540$2c9a31d2@co3007967a> From: "Travis Howell" To: "Max Yang" , References: Subject: Re: 1.3.10:Problem Building Object Files of modules,Eggdrop 1.6.10 Date: Tue, 7 May 2002 21:36:35 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 From: "Max Yang" > I've tried to port eggdrop1.6.10 via Cygwin 1.3.10 > In case of "Make" > I got error messages as shown > /*------------------------------------------------------- > make[1]: Entering directory `/cygdrive/f/windrop/src/mod' > ',needed by `modules'. Stop.arget `assoc.mod_so > make[1]: Leaving directory `/cygdrive/f/windrop/src/mod' > make: ***[debmodules] Error 2 > -------------------------------------------------------*/ > And when I tried "Make Static" > The error messages were > /*------------------------------------------------------- > make[1]: Entering directory `/cygdrive/f/windrop/src/mod' > ', needed by `static'. Stop.target `assoc.mod_o > make[1]: Leaving directory `/cygdrive/f/windrop/src/mod' > make: ***[static] Error 2 > -------------------------------------------------------*/ > I've tried to trace the porting processes > And I've found there were no any object files of modules has been created > How do I solve it? I have not run into that problem with a Eggdrop compile under Cygwin before, sounds like Cygwin isn't be detected correctly though since _so files are been used. Try the Eggdrop for Windows binaries at http://windrop.sourceforge.net/ -- 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/