I also had a similar experience trying to build gcc6 on my Edgerouter Lite (same model as linked on tedu's blog page, which is how I discovered this little machine initially) on a snapshot from ~2 weeks ago. MP kernel, with the ERL's /usr/ports on an NFS volume hosted by an amd64 OpenBSD system.
I had a 'vmstat 15' running in another terminal throughout and it did dip down into low double-digits a few minutes before the segfault I realise this post is not terribly useful other than being a "me too". If it's worth my trying a non-MP kernel I'll do that and report back John On 1 January 2018 at 05:52, Janne Johansson <icepic...@gmail.com> wrote: > > 2017-12-30 5:01 GMT+01:00 Diana Eichert <deich...@wrench.com>: > > > Hi misc@ long time since I posted > > > > collect2: error: ld terminated with signal 11 [Segmentation fault] > > > > while building gcc-4.9.4 package on Ubiquiti Unifi Security Gateway > > > > I'm running 12/22/2017 octeon snapshot, bsd.mp GENERIC.MP kernel. > > > > System built 109 packages before Seg Fault when building gcc-4.9.4 > > > > > I think I got those on my Octeon also, but I thought gcc had figured out a > way to drive my > box into swap and die so I just stopped trying to build gcc from ports. > > > -- > May the most significant bit of your life be positive.
