Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "ted byers" To: "'Mumit Khan'" Cc: Subject: RE: building gcc/g++ seems OK but building g77 seems to be seriously broken Date: Tue, 17 Jul 2001 18:57:09 -0400 Message-ID: <003001c10f13$cfbbc830$5c66e740@beak.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Disposition-Notification-To: "ted byers" Thanks Mumit, Oh OK, The configure command I used was: $ ../Source/gcc-3.0/configure --prefix=/usr/local/gcc-3.0 --enable-threads --d isable-win32-registry --enable-sjlj-exceptions --with-included-gettext --ena ble-languages='c++,f77' What is the "-lm", and is there anything I can do about it? I would like to test this, so I can verify whether or not g77 is working correctly. I want to experiment with mixed language programming using fortran and C++ (because most of my development is based primarily in C++, but there is an incredible wealth of number crunching libraries available in fortran). However, if I encounter a problem, I do not want to have to worry that something I did when building g77 might have broken it in a way that precludes what I am attempting from working correctly. Thanks again, Ted -----Original Message----- From: Mumit Khan [mailto:khan AT NanoTech DOT Wisc DOT EDU] Sent: Tuesday, July 17, 2001 6:24 PM To: ted byers Cc: cygwin AT cygwin DOT com Subject: Re: building gcc/g++ seems OK but building g77 seems to be seriously broken On Tue, 17 Jul 2001, ted byers wrote: > Well, I have now built GCC3 a couple times, trying to figure out what has > gone awry, but nothing seems to fix g77 (the summary given below show why I > think it is seriously broken). gcc and g++ seem to be OK since their > respective test suites give the expected results (the number of unexpected > failures being extemely small). When you report gcc build problems, you really need to provide the flags you passed to configure. Too many variables otherwise. > === g77 Summary === > > # of expected passes 281 > # of unexpected failures 334 > # of untested testcases 326 > /home/Bted/Objects/gcc/g77 g77 version 3.0 (Fortran Frontend version 0.5.26 > 20010617 (experimental)) Probably a problem in the g77 tests, which passes the -lm, and that causes a problem on Cygwin 1.1.x. Regards, Mumit -- 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/