Date: Mon, 21 Feb 2022 11:09:37 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251117] [NEW PORT] www/palemoon: Open-source web browser Message-ID: <bug-251117-7788-elhBdirEnD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251117-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-251117-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251117 --- Comment #82 from Olivier Certner <olivier.freebsd@free.fr> --- Sorry for the delay. I do not reproduce the errors you report on a recent 12.3-STABLE. (In reply to Kurt Jaeger from comment #80) I've never seen that error about old-configure.in having changed after the configure phase has been run (and the log seems to indicate that old-config= ure was refreshed from old-configure in directory platform/). On a successful build, I strangely have an empty platform/configure (although there is a configure.in) and platform/old-configure is in place and seems valid. Don't know much about poudriere, but could it be that it messes with the timestamp of files between build phases? Could you relaunch the build just = to see if this was something transient (e.g., due to a race condition in the build)? (In reply to Gleb Popov from comment #81) Never seen this error either. Seems to be a JS stack overflow. On which architecture are you building? Is it 32-bit on amd64? Thanks. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251117-7788-elhBdirEnD>