Subject: Re: GCC 3.3.3 import sometime soon
To: None <port-alpha@NetBSD.org>
From: Paul Mather <paul@gromit.dlib.vt.edu>
List: port-alpha
Date: 03/05/2004 14:30:36
On Fri, Mar 05, 2004 at 10:25:18AM -0500, Paul Mather wrote:

=> I don't know about broken builds, but I am getting problems building
=> packages with the native GCC 3.3.3.
[...]
=> I should probably try a fresh CVS update and a kernel+userland
=> rebuild to see if it helps...

Well, I guess things just got a lot more dicey, as my latest attempt
to rebuild tools, kernel, and userland failed.  It stops when
rebuilding tools, in groff:

>>>>>
===> build.sh command: ./build.sh -T /usr/tools -D /home/netbsd -r tools kernel=CHUMBY kernel=HAWKWIND distribution
===> build.sh started: Fri Mar  5 10:45:21 EST 2004
===> Bootstrapping nbmake
checking for sh... /bin/sh
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
[[...]]
#      link  zic/zic
cc -O -DNOID -I/usr/src/tools/compat/obj -I/usr/src/tools/compat/obj/include  -I/usr/src/tools/zic/../compat -DHAVE_NBTOOL_CONFIG_H=1  -D_FILE_OFFSET_BITS=64 -D_NETBSD_SOURCE  -Dunix   -o zic zic.lo scheck.lo ialloc.lo -L/usr/src/tools/compat/obj -lnbcompat -lz
dependall ===> groff
checking for gcc... cc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ANSI C... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking that C++ compiler can compile simple program... no
configure: error: a working C++ compiler is required

*** Failed target:  .configure_done
*** Failed command: (cd build && CC=cc CFLAGS=-O CPPFLAGS=\ -I/usr/src/tools/compat/obj\ -I/usr/src/tools/compat/obj/include\ \ -I/usr/src/tools/groff/../compat\ -DHAVE_NBTOOL_CONFIG_H=1\ \ -D_FILE_OFFSET_BITS=64\ -D_NETBSD_SOURCE CXX=c++ CXXFLAGS=-O INSTALL=/usr/tools/bin/nbinstall\ -c\ \ -r LDFLAGS= LEX=/usr/tools/bin/nblex PATH="/usr/tools/bin:$PATH" YACC=/usr/tools/bin/nbyacc sh /usr/src/tools/groff/../../gnu/dist/groff/configure --prefix=/usr/tools)
*** Error code 1

Stop.
nbmake: stopped in /usr/src/tools/groff

*** Failed target:  dependall
*** Failed command: cd /usr/src/tools/groff; /usr/tools/bin/nbmake realall
*** Error code 1

Stop.
nbmake: stopped in /usr/src/tools/groff

*** Failed target:  dependall-groff
*** Failed command: targ=dependall;dir=groff; case "$dir" in /*) echo "$targ ===> $dir"; cd "$dir"; /usr/tools/bin/nbmake "_THISDIR_=$dir/" $targ; ;; *) echo "$targ ===> $dir"; cd "/usr/src/tools/$dir"; /usr/tools/bin/nbmake "_THISDIR_=$dir/" $targ; ;; esac
*** Error code 1

Stop.
nbmake: stopped in /usr/src/tools

ERROR: Failed to make tools
*** BUILD ABORTED ***
<<<<<

It does look like a new c++ was built, though, before the build
failed:

>>>>>
~ paul@chumby$ /usr/tools/bin/alpha--netbsd-c++ -v
Reading specs from /usr/tools/lib/gcc-lib/alpha--netbsd/3.3.3/specs
Configured with: /usr/src/tools/gcc/../../gnu/dist/gcc/configure --target=alpha--netbsd --disable-nls --enable-long-long --disable-multilib --enable-threads --program-transform-name=s,^,alpha--netbsd-, --enable-languages=c c++ objc f77 --prefix=/usr/tools
Thread model: posix
gcc version 3.3.3 (NetBSD nb1 20040301)
~ paul@chumby$ c++ -v
Using built-in specs.
Configured with: /home/nick/work/netbsd/src/tools/gcc/../../gnu/dist/gcc/configure --enable-long-long --disable-multilib --enable-threads --disable-symvers --build=i386-unknown-netbsdelf --host=alpha--netbsd --target=alpha--netbsd
Thread model: posix
gcc version 3.3.3 20040209 (prerelease/NetBSD)
<<<<<

I was under the impression that the build system is (relatively)
self-contained.  So, is my build failing because the current c++ is
broken on alpha, or because my installed c++ is apparently broken (via
a recent update; see previous message to which this one is followup)?
If the latter, what is the best way to fix things (install comp.tgz
from a non-broken snapshot?)?

Cheers,

Paul.

e-mail: paul@gromit.dlib.vt.edu

"Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid."
        --- Frank Vincent Zappa