Date: Thu, 01 Aug 2024 03:42:43 +0000 From: bugzilla-noreply@freebsd.org To: uboot@FreeBSD.org Subject: [Bug 280544] u-boot doesn't build with -j32 Message-ID: <bug-280544-39090-moBNCIb2P8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280544-39090@https.bugs.freebsd.org/bugzilla/> References: <bug-280544-39090@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=3D280544 --- Comment #2 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Mark Millard from comment #1) For the sucessful build, I show the CONFIG_DFU_NAND text and some of what comes just after: Value of CONFIG_DFU_NAND is redefined by fragment configs/bbb_fragment: Previous value: CONFIG_DFU_NAND=3Dy New value: CONFIG_DFU_NAND=3Dn gmake[1]: Entering directory '/wrkdirs/usr/ports/sysutils/u-boot-beaglebone/work/u-boot-2024.04' HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o YACC scripts/kconfig/zconf.tab.c LEX scripts/kconfig/zconf.lex.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --alldefconfig Kconfig # # configuration written to .config # gmake[1]: Leaving directory '/wrkdirs/usr/ports/sysutils/u-boot-beaglebone/work/u-boot-2024.04' NOTE: that the above is what produces the .config file. This is very different than the error message about a bad option J passed to gmake that is reported in the log file that you attached. That in turn lead to no .config file being produced. That in turn lead to later errors in your build log. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-280544-39090-moBNCIb2P8>