1a. If I type ./configure with no additional options and type "make" then I get a "default" build of the toolchain. 2a. If I type ./configure with no additional options and type "make profiledbootstrap" then I get a profiled, "default" build of the "c" and "ada" portion toolchain. (a bug report about that is filed elsewhere) 3a. If I type ./configure with "--enable-coverage=noopt" and type "make" then I get a "coverage-checking", "default" build of the toolchain. 1b. ./configure with no additional options and typing "make" produces no output that mentions "profiling" - OK 2b. ./configure with no additional options and typing "make profiledbootstrap" produces a comment that mentions "profiling" - OK 3b. ./configure with "--enable-coverage=noopt" and typing "make" produces a comment that mentions "profiling" - BUG When you are NOT making a profiledbootstrap the Makefile is displaying "Configuring stage profile in ./intl" -- It is using the same text when you check coverage as when you collect profiling stats. A different message for different operations would be less confusing: Old: Configuring stage profile in ./intl New: Configuring stage coverage in ./intl # ./configure with "--enable-coverage=noopt" ... # gmake ... gmake[4]: Entering directory `/usr/share/src/gcc_build/i386-pc-solaris2.11/libgcc' /bin/sh ../../../gcc_trunk/libgcc/../mkinstalldirs ../.././gcc /usr/bin/ginstall -c -m 644 libgcc_eh.a ../.././gcc/ chmod 644 ../.././gcc/libgcc_eh.a /usr/local/i386-pc-solaris2.11/bin/ranlib ../.././gcc/libgcc_eh.a /bin/sh ../../../gcc_trunk/libgcc/../mkinstalldirs ../.././gcc; /usr/bin/ginstall -c -m 644 ./libgcc_s.so.1 ../.././gcc/libgcc_s.so.1; rm -f ../.././gcc/libgcc_s.so; ln -s libgcc_s.so.1 ../.././gcc/libgcc_s.so /bin/sh ../../../gcc_trunk/libgcc/../mkinstalldirs ../.././gcc /usr/bin/ginstall -c -m 644 libgcc.a ../.././gcc/ chmod 644 ../.././gcc/libgcc.a /usr/local/i386-pc-solaris2.11/bin/ranlib ../.././gcc/libgcc.a /usr/bin/ginstall -c -m 644 libgcov.a ../.././gcc/ chmod 644 ../.././gcc/libgcov.a /usr/local/i386-pc-solaris2.11/bin/ranlib ../.././gcc/libgcov.a parts="gmon.o crtbegin.o crtend.o"; \ for file in $parts; do \ rm -f ../.././gcc/$file; \ /usr/bin/ginstall -c -m 644 $file ../.././gcc/; \ done gmake[4]: Leaving directory `/usr/share/src/gcc_build/i386-pc-solaris2.11/libgcc' gmake[3]: Leaving directory `/usr/share/src/gcc_build/i386-pc-solaris2.11/libgcc' gmake[2]: Leaving directory `/usr/share/src/gcc_build' gmake[2]: Entering directory `/usr/share/src/gcc_build' gmake[3]: Entering directory `/usr/share/src/gcc_build' rm -f stage_current gmake[3]: Leaving directory `/usr/share/src/gcc_build' gmake[2]: Leaving directory `/usr/share/src/gcc_build' gmake[2]: Entering directory `/usr/share/src/gcc_build' Configuring stage profile in ./intl
Well you don't understand any of these options it seems. First --enable-coverage=nopt does nothing except changes the CFLAGS really. There is nothing in the toplevel makefile or configure which uses --enable-coverage=, only the gcc subdirectory. Also you should not be bootstrapping a compiler built with --enable-coverage= really.
(In reply to comment #1) > Well you don't understand any of these options it seems. > First --enable-coverage=nopt does nothing except changes the CFLAGS really. > There is nothing in the toplevel makefile or configure which uses > --enable-coverage=, only the gcc subdirectory. Also you should not be > bootstrapping a compiler built with --enable-coverage= really. > I only typed make, what should I have done to start the build after configuring ? Rob