On May 30, 2025, at 10:43, Dag-Erling Smørgrav <[email protected]> wrote:
> Mark Millard <[email protected]> writes: >> Dag-Erling Smørgrav <[email protected]> writes: >>> This is preceded by an 800-line list of warnings from a single source >>> file (multi_index_block.cpp). This list is clearly truncated as it's >>> missing the final “N warnings generated” line, so my guess is there is >>> at least one error there as well which just doesn't get displayed. >> My guess: the failure occurred while the warnings were otherwise >> still being generated and that is what stopped the warnings. > > That's possible. If we assume that the error code returned by scons is > an errno, it corresponds to EBADF. Perhaps a bug in scons causes it to > lose track of the pipe it uses to read the compiler's stderr. devel/scans has not been updated after 2024-Jun-06: QUOTE author Po-Chuan Hsieh <[email protected]> 2024-06-06 22:03:56 +0000 committer Po-Chuan Hsieh <[email protected]> 2024-06-06 22:03:56 +0000 . . . devel/scons: Update to 4.7.0 Changes: https://github.com/SCons/scons/releases https://scons.org/tag/releases.html PR: 279488 Exp-run by: antoine END QUOTE That would mean that quarterly got the update in 2024 as well. https://pkg-status.freebsd.org/ampere1/data/141arm64-quarterly/2e2d801cf977/logs/mongodb60-6.0.18.log did not fail but shows the warnings. devel/scons does not seem to be the source of the change in beavior. === Mark Millard marklmi at yahoo.com
