Re: NetBSD-HEAD amd64 refuses to build

["Thomas Mueller" <mueller6724%bellsouth.net@localhost>]

> Since -current had some "hard times" in the last few weeks, and maybe
> not everyone is aware of this site:
        
>   http://releng.netbsd.org/cgi-bin/builds.cgi
        
> shows the status of the last autobuilds. We already had one working
> -current (HEAD) build this week, yay!
        
> As you can see there, the stable branches rarely fail to build. When
> they do, it either is a spurious problem of the autobuild system (e.g.
> running out of disk space), or a broken pullup, that will usualy be
> fixed within a few hours.
        
> If you try to build one of the stable branches locally (from clean
> source trees and empty obj dir), and fail, this either is a clear
> failure in the "tools" phase (e.g. when you build on some host system
> that hasn't been tested lately), in this case: file a PR.
> Or: you are passing some "strange" options to build.sh, e.g. an inconsistent
> or not supported mixture of MK...=YES/NO flags. You should not fiddle with
> those flags normally, unless you clearly understand all implications and
> are willing to fix the fallout.

> Martin

> I still don't understand what you're trying to do, or why you're
> apparently surprised it doesn't work.
        
--
> David A. Holland
> dholland%netbsd.org@localhost

I've been following that website consistently for many months.

Most of the time, even recently, HEAD built successfully for amd64 and i386.

I keep getting Internal compiler error, segmentation fault when using base gcc,
without any strange or fancy stuff in build.sh command.

Possibly with gcc not being upgraded while mpc, mpfr and gmp have been (?), 
something is out of sync?  But I was able to build lang/clang and also gcc48
and gcc-aux from pkgsrc, so I thought maybe not rebuild base gcc.

But there was another suggestion to put -std=c++0x or -std=gnu++0x , and I 
wanted to know where to do that for build.sh .

I updated NetBSD 6.1_STABLE on other computer, and for the first time, was
successful booting on MSI Z77 MPOWER motherboard.  Maybe the result of five
months of improvements?

Tom