This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Tutorial 4b
- From: Mark Butcher <M_J_BUTCHER at compuserve dot com>
- To: "INTERNET:huntbs at lycos dot com" <huntbs at lycos dot com>
- Cc: gcc <gcc at gcc dot gnu dot org>, gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Wed, 26 Jun 2002 17:58:11 -0400
- Subject: Re: Tutorial 4b
Hi Brett
As Peter has explained, the build process seems to be correct - build
binutils, build a simple c-compiler without libraries, build the newlib
libraries with the simple compiler.
In the fourth step the simple c compiler is used to build the c++ compiler
(for this it needs the libraries from the previous step).
I don't know the exact order of what happens during the fourth step but I
assume it must build the c++ compiler before it starts on the c++ library
sources. In fact my script is dumb and continues with the install process
after the build fails to complete the libraries. In the process it has
added mcore-elf-c++.exe and mcore-elf-g11.exe to the destination /bin
directory.
Therefore it seems as though the gcc tools have indeed been successfully
built and the issue is purely a library issue. Perhaps the result is
useable as long as the missing library routines are not required for the
specific program. Up to now my whole energy has been devoted to getting the
compiler built and so I don't yet have any experience with actually using
it and its libraries so can not yet guage how important or irrelevent the
missing library components are.
Cheers
Mark