Re: gcc/cpp segfaulting on i386-9.99.17?

["John D. Baker" <jdbaker%consolidated.net@localhost>]

On Sat, 26 Oct 2019, John D. Baker wrote:

> On Wed, 23 Oct 2019, John D. Baker wrote:
> 
> > Anyone else tried building gstreamer1 or at-spi2-core on i386-9.99.17?
> 
> Note that I mention the i386 port specifically.  I have observed the
> segfaults only on i386-current.  amd64-current does not exhibit the
> problem.  (My amd64-current systems have not yet been updated with GCC-8,
> so they still use GCC 7.4.0 as well.)

To be honest, I don't remember if the previous amd64/GCC7 build session
(pkg_rr) ever got to gstreamer1 or at-spi2-core (my NFS root w/local-disk
"/usr") bogged my network and file server down worse than an all-NFS
diskless system and that's with ${WRKOBJDIR} on tmpfs!).

I've now built gstreamer1 on amd64 w/GCC 8.3.0 and it completed
successfully.  A look at the package database shows at-spi2-core
was also successfully built.

The thread here:

  http://mail-index.netbsd.org/pkgsrc-users/2019/10/24/msg029718.html

reported similar failures building pango.

As I was composing this message, my amd64/GCC-8 build host completed
building pango without issues.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645