Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sources DOT redhat DOT com
From: "ted byers" <ted DOT byers AT sympatico DOT ca>
To: <cygwin AT cygwin DOT com>
Subject: Building gcc3.0 appears to have worked
Date: Fri, 13 Jul 2001 16:12:02 -0400
Message-ID: <002d01c10bd8$14caa1b0$7069e740@beak.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
Disposition-Notification-To: "ted byers" <ted DOT byers AT sympatico DOT ca>

Following the advice kindly provided by Mr Prince and Mr Kahn, it appears
that I have been able to get gcc 3.0 to compile.  However, I have a couple
questions.  Some of these may be due to the fact it has been a while since I
have used unix, so ...

I observed the following errors that occured during the build, but make
appeared to ignore them.  Should I be concerned about them?

=======build errors from log=================

mv: cannot stat `s-crt0': No such file or directory
mv: cannot stat `gcc-cross.exe': No such file or directory
mv: cannot stat `cc1obj.exe': No such file or directory
mv: cannot stat `enquire.exe': No such file or directory
mv: cannot stat `protoize.exe': No such file or directory
mv: cannot stat `unprotoize.exe': No such file or directory
mv: cannot stat `collect2.exe': No such file or directory
mv: cannot stat `gcov.exe': No such file or directory
mv: cannot stat `*.[0-9][0-9].*': No such file or directory
mv: cannot stat `*.[si]': No such file or directory
mv: cannot stat `g++-cross.exe': No such file or directory
mv: cannot stat `cc1plus.exe': No such file or directory
mv: cannot stat `g77.exe': No such file or directory
mv: cannot stat `g77-cross.exe': No such file or directory
mv: cannot stat `f771.exe': No such file or directory
make[2]: [stage1-start] Error 1 (ignored)


mv cp/*.o stage1/cp
mv: cannot stat `cp/*.o': No such file or directory
make[2]: [c++.stage1] Error 1 (ignored)


mv: cannot stat `s-crt0': No such file or directory
mv: cannot stat `gcc-cross.exe': No such file or directory
mv: cannot stat `cc1obj.exe': No such file or directory
mv: cannot stat `enquire.exe': No such file or directory
mv: cannot stat `protoize.exe': No such file or directory
mv: cannot stat `unprotoize.exe': No such file or directory
mv: cannot stat `collect2.exe': No such file or directory
mv: cannot stat `*.[0-9][0-9].*': No such file or directory
mv: cannot stat `*.[si]': No such file or directory
mv: cannot stat `g++-cross.exe': No such file or directory
mv: cannot stat `g77-cross.exe': No such file or directory
make[2]: [stage2-start] Error 1 (ignored)
mv intl/*.o stage2/intl


mv: cannot stat `g77spec.o': No such file or directory
mv: cannot stat `g77version.o': No such file or directory
make[2]: [f77.stage2] Error 1 (ignored)
make[2]: Leaving directory `/home/Bted/Objects/gcc'

===============end of build errors=======================

I also ran the test suite and, ten hours later, observed the following
results

		=== gcc Summary ===

# of expected passes		15203
# of unexpected failures	9
# of unexpected successes	3
# of expected failures		85
# of unresolved testcases	1
# of unsupported tests		25
Executing on host: /home/Bted/Objects/gcc/xgcc -v    (timeout = 300)
spawn /home/Bted/Objects/gcc/xgcc -v  Using builtin specs. Configured with:
../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 Thread model: win32 gcc version 3.0
/home/Bted/Objects/gcc/xgcc version 3.0

runtest completed at Sat Jul  7 02:30:31 2001


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


I suppose that this means that gcc 3.0, as built on my system is reasonably
usable.  But I would also suppose that g77 is so seriously broken as to be
unusable.  Would that be correct?

Also, when I query gcc from the cygwin bash prompt, it seems to think it is
gcc 2.95.?, so it would seem that although the binaries were built and put
where I configured them to be put, it is the old ones that I will get when I
compile from the bash prompt.  So the question is, how can I control which
version of gcc I am using, assuming I will want to leave both intact (for
testing purposes), and ensure that each searches its own include path, and
this without having to type the full path to each set of binaries?

Finally, I had emacs installed long before I installed cygwin (but I am
still a little rusty with it).  How can I tell it, in one session, to use
the older version of gcc, or, in another session, to use the newer version?

Any advice would be greatly appreciated.

Cheers,

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/