Don't know about AMD, but on ARM failures that resemble this are common. In some cases the actual error message is tens or a hundred lines prior to the last make output.
If you search for the string Error: or maybe error: does anything show up? Including the colon : helps to reduce irrelevant hits. Good luck, bob prohaska On Sun, Jun 07, 2020 at 04:27:24PM +0000, Filippo Moretti wrote: > Good evening,???????????????????????????????????????????????? FreeBSD sting > 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r361787: Sun Jun?? 7 15:02:09 CEST > 2020???????? root@sting:/usr/obj/usr/src/amd64.amd64/sys/STING?? amd64 > > the build fails with the following message/common/extensions/api/action.json > ../../chrome/common/extensions/api/browser_action.json > ../../chrome/common/extensions/api/browsing_data.json > ../../chrome/common/extensions/api/extension.json > ../../chrome/common/extensions/api/idltest.idl > ../../chrome/common/extensions/api/page_action.json > ../../chrome/common/extensions/api/top_sites.json > ninja: build stopped: subcommand failed. > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/www/chromium > > ===>>> make build failed for www/chromium > ===>>> Aborting update > > I enclose the list of packages installedsincerelyFilippo > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
