Re: pkg/60266 (firefox140: Build fails with a catastrophic number of build errors)

["opensauce04%gmail.com@localhost via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR pkg/60266; it has been noted by GNATS.

From: opensauce04%gmail.com@localhost
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: pkg/60266 (firefox140: Build fails with a catastrophic number of
 build errors)
Date: Fri, 14 Aug 2026 22:07:52 +0100

 Hi, sorry for not replying to this for such a long time.
 
 The install where I was encountering this issue is long-gone, and I
 haven't and will continue to not have time to look into this issue or
 attempt to recreate it. If it seems fine on your end, this was more
 than likely just some fluke or mistake on my end, and the report can
 be closed. Thanks for your time!
 
 
 On 17/05/2026 02:10, David H. Gutteridge via gnats wrote:
 > The following reply was made to PR pkg/60266; it has been noted by GNATS.
 >
 > From: "David H. Gutteridge" <david%gutteridge.ca@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc:
 > Subject: Re: pkg/60266 (firefox140: Build fails with a catastrophic number
 >   of build errors)
 > Date: Sat, 16 May 2026 21:09:02 -0400
 >
 >   There must be something different about the environment here, as this
 >   certainly does successfully build on recent NetBSD releases. For
 >   example, the TNF build infrastructure for 11.0 using the 2026Q1 branch
 >   has generated a package for 140.10.2:
 >   
 >   https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/11.0_2026Q1/All/fi=
 >   refox140-140.10.2.tgz
 >   
 >   It also builds on relatively recent NetBSD 11.99.5/amd64, as I'm
 >   running it there right now.
 >   
 >   The output provided doesn't seem too helpful. What's needed is the
 >   original error that has occurred. To capture a full build log, one can
 >   simply use script(1) to save to a file, e.g.,
 >   
 >   script build.log
 >   make
 >   exit (to stop the script)
 >   
 >   Then either share the complete log somewhere (attaching to GNATS
 >   wouldn't work well), or, find the spot where the errors first appear
 >   (using a text editor, perhaps).
 >   
 >   It would also help to know more about the underlying environment, e.g.,
 >   if there are any non-standard pkgsrc settings.
 >   
 >   Regards,
 >   
 >   Dave
 >   
 >   PS There's nothing "catastrophic" about this, it's simply a build
 >   failure where parsing has become troubled, so the compiler emits a
 >   bunch of errors as it progresses through a (complex) file.
 >