Date: Sat, 17 Feb 2018 23:36:34 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 224217] [patch] Fix cross build of base/ ports Message-ID: <bug-224217-32340-znufilLqO4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224217-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-224217-32340@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=3D224217 --- Comment #27 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to commit-hook from comment #22) base/binutils/pkg-plist.sparc64 and base/binutils/pkg-plist.powerpc64 list: bin/as bin/ld bin/ld.bfd bin/objcopy bin/objdump This appears to imply that the README's sparc64 example lines: 2/ cross build world make CROSS_TOOLCHAIN=3Dsparc64-gcc TARGET=3Dsparc64 TARGET_ARCH=3Dsparc64 b= uildworld are intended to be based on (implicitly or explicitly) WITHOUT_BINUTILS=3D so that the files listed are only from base/binutils . This is likely because the system binutils are insufficient in some cases for the likes of, at least, powerpc64. WITHOUT_BINUTILS=3D is the default only for arm64/aarch64, riscv/riscv64, and riscv/riscv64sf according to the man src.conf that I'm reading. (It turns out my normal/historical cross-builds include the system binutils by not having been explicit to avoid such, both for system-clang based builds and for powerpc64-xtoolchain-gcc based builds: Not the best way to test base/binutils use. My test target-context here is: powerpc64.) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224217-32340-znufilLqO4>