Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"ted byers" <ted DOT byers AT sympatico DOT ca>
To:	<cygwin AT cygwin DOT com>
Subject:	building gcc/g++ seems OK but building g77 seems to be seriously broken
Date:	Tue, 17 Jul 2001 17:19:27 -0400
Message-ID:	<002d01c10f06$2987ca70$2371e740@beak.com>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Disposition-Notification-To:	"ted byers" <ted DOT byers AT sympatico DOT ca>

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).

I created logs of the build and tes by redirecting all output into make.log
and test.log.

The only thing I can see of potential concern related to the build of g77 is
the following near the end of stage 2:

mv cp/*.o stage2/cp
if [ -f lang-f77 ]; then \
  mv -f f/*.o f/fini.exe f/stamp-str f/str-*.h f/str-*.j lang-f77 g77spec.o
g77version.o stage2/f; \
fimv: cannot stat `g77spec.o': No such file or directory
mv: cannot stat `g77version.o': No such file or directory

This is puzzling since I can see a number of places earlier in the log where
these two files are compiled.

And the, in test.log, near the beginning of each suite of tests I see the
following warning (and usually the second warning):
WARNING: Couldn't find the global config file.
WARNING: Couldn't find tool init file

I do not know if this means that my installation of cygwin is broken or if
there is something missing from the source code distribution I have for
gcc3.

The following is excerpted from the g77 tests.  Of course, I am not about to
waste bandwidth by sending the entire results, but what appears to be the
salient portions are included here.

(rootme=`pwd`; export rootme; \
srcdir=`cd ../../Source/gcc-3.0/gcc; pwd` ; export srcdir ; \
cd testsuite; \
EXPECT=expect ; export EXPECT ; \
if [ -f ${rootme}/../expect/expect ] ; then  \
   TCL_LIBRARY=`cd .. ; cd ../../Source/gcc-3.0/gcc/../tcl/library ; pwd` ;
\
   export TCL_LIBRARY ; fi ; \
runtest --tool g77 )
WARNING: Couldn't find the global config file.
Test Run By Bted on Sun Jul 15 22:32:58 2001
Native configuration is i686-pc-cygwin

		=== g77 tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /home/Bted/Source/gcc-3.0/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /home/Bted/Source/gcc-3.0/gcc/testsuite/g77.dg/dg.exp ...
FAIL: g77.dg/20010216-1.f (test for excess errors)
WARNING: g77.dg/20010216-1.f compilation failed to produce executable
FAIL: g77.dg/20010216-1.f (test for excess errors)
WARNING: g77.dg/20010216-1.f compilation failed to produce executable
... lots o' lines - all indicating some kind of failure

		=== 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))

make[1]: [check-g77] Error 1 (ignored)

Clearly something is broken in g77 in order for there to be well over two
thirds of the tests either unexpectedly failing or not being run for some
reason.  Is this something I can fix, and if so how?

I have already tried deleting and rebuilding libf2c, but to no effect.

Any suggestions would be welcome.

Thanks,

Ted

R.E. Byers
ted DOT byers AT sympatico DOT ca


--
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/

- Raw text -