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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Mon, 12 Jan 2004 12:56:38 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Gabriel SOUBIES cc: cygwin AT cygwin DOT com Subject: RE: Problem compiling cygwin1.dll from CVS In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII By "exactly the same build problem" I assume you mean a parse error in line 4 of cygwin.def? Could you please attach (*not* include inline) your generated cygwin.def, the output of "cygcheck -svr" on your system, the exact flags you're passing to "configure", and the exact command that fails? Igor On Mon, 12 Jan 2004, Gabriel SOUBIES wrote: > I experienced exactly the same build problem and all my mounts are binary > mounts... > So far I have not been able go further than this error. > If someone can help us, he is really welcome! > Thx > > -----Message d'origine----- > De : cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]De la part > de Igor Pechtchanski > Envoye : vendredi 26 decembre 2003 17:12 > A : Nuno Ferreira > Cc : cygwin AT cygwin DOT com > Objet : Re: Problem compiling cygwin1.dll from CVS > > On Fri, 26 Dec 2003, Nuno Ferreira wrote: > > > Hi, > > while trying to find a problem with an application I'm using (that by > > the way was corrected by yesterday's snapshot) I tried to compile the > > DLL from CVS and it failed with this error: > > [snip] > > collect2: ld terminated with signal 11 [Segmentation fault], core dumped > > /usr/lib/gcc-lib/i686-pc-cygwin/3.3.1/../../../../i686-pc-cygwin/bin/ld: cygwin.def:4: parse error > > make[2]: *** [cygwin0.dll] Error 1 > > > > The created cygwin.def follows, do you have any ideia what can cause > > this problem? > > At a guess, judging from the CRLF line endings in the first 3 lines, > you're trying to build Cygwin on a text mount. Thus, ld expects to see > all lines ending in CRLF. However, gcc seems to write the defs with LFs > explicitly, so ld sees line 4 as one long line, and gives a parse error. > I'd suggest moving the build to a binary mount and trying again. > > > Also, I am experiencing some major memory leaks using the application, > > the same application runs flawlessly in linux, does anyone know any tool > > (something similar to valgrind) I can use to track the leaks under > > cygwin? > > > > Thank you > > -- > > Nuno > > Doesn't Cygwin use Doug Lea's malloc? I thought it had some leak > detection routines (or, at least, routines to print memory stats). Take a > look at winsup/cygwin/malloc.cc... > Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/