Date: Sun, 13 Aug 2023 10:50:03 -0700 From: Mark Millard <marklmi@yahoo.com> To: Juraj Lutter <otis@FreeBSD.org> Cc: Current FreeBSD <freebsd-current@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, Mike Karels <mike@karels.net> Subject: Re: Error crosscompiling 14.0-ALPHA1 on amd64 for arm64.aarch64 Message-ID: <D12F81D5-20E3-4275-96FE-F6C258618C19@yahoo.com> In-Reply-To: <3D94C0A3-0231-4C04-8C69-5516A4A41B03@FreeBSD.org> References: <2A8F9F90-B03C-4A7B-9B03-B54386CEBBAE.ref@yahoo.com> <2A8F9F90-B03C-4A7B-9B03-B54386CEBBAE@yahoo.com> <3D94C0A3-0231-4C04-8C69-5516A4A41B03@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 13, 2023, at 10:10, Juraj Lutter <otis@FreeBSD.org> wrote: > Mark, >=20 >> On 13 Aug 2023, at 19:04, Mark Millard <marklmi@yahoo.com> wrote: >>=20 >> No arm64.aarch64/tmp/ SYSTEM_COMPILER or SYSTEM_LINKER bootstrap = compiler/linker were built. >>=20 >> =46rom what I can tell, this leads to: >>=20 >> cc -march=3Darmv7 -m32 -target armv7-unknown-freebsd14.0-gnueabihf = -DCOMPAT_LIBCOMPAT=3D\"32\" -DCOMPAT_libcompat=3D\"32\" -DCOMPAT_LIB32 = --sysroot=3D/usr/obj/usr/src/arm64.aarch64/tmp = -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin = -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/lib32 -O2 -pipe -fno-common = -fPIC -g -gz=3Dzlib -MD -MF.depend.libssp_nonshared.o = -MTlibssp_nonshared.o -std=3Dgnu99 -Wno-format-zero-length = -fstack-protector-strong -Wsystem-headers -Werror -Wall -Wno-format-y2k = -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes = -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch = -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts = -Wnested-externs -Wold-style-definition -Wno-pointer-sign -Wdate-time = -Wmissing-variable-declarations -Wthread-safety -Wno-empty-body = -Wno-string-plus-int -Wno-unused-const-variable = -Wno-error=3Dunused-but-set-parameter -Qunused-arguments -c = /usr/src/lib/libssp_nonshared/libssp_nonshared.c -o libssp_nonshared.o >>=20 >> using the pre-existing system compiler that, in your context, gets: >>=20 >> error: unable to create target: 'No available targets are compatible = with triple "armv7-unknown-freebsd14.0-gnueabihf"' >> 1 error generated. >>=20 >=20 > True, exactly the same error I=E2=80=99m getting. It was extracted from a copy of your log file. >> I doubt that "make package" was tested for being able to handle >> the lib32 addition to aarch64 builds for SYSTEM_COMPILER or >> SYSTEM_LINKER bootstrap cases. >>=20 >=20 > I=E2=80=99m getting it in buildworld, not in packages (it does not = come to packages target) >=20 Sorry. Looks like I misapplied one of your messages mentioning use of "make package" as specifying the context for the log file. Still, your log file does not show an arm64.aarch64/tmp/ time frame build of the SYSTEM_COMPILER or SYSTEM_LINKER bootstrap compiler/linker. There should have also been: tmp/obj-tools/lib/clang/libllvm...] tmp/obj-tools/lib/clang/libclang...] tmp/obj-tools/lib/clang/headers...] tmp/obj-tools/usr.bin/clang/clang...] tmp/obj-tools/usr.bin/clang/lld...] to go with: make[1]: "/usr/src/Makefile.inc1" line 340: SYSTEM_COMPILER: libclang = will be built for bootstrapping a cross-compiler. make[1]: "/usr/src/Makefile.inc1" line 345: SYSTEM_LINKER: libclang will = be built for bootstrapping a cross-linker. So it still looks to me like a build infrastructure problem: it did not do what it said it would do. I've no clue about why at this point. I'll note that clang and lld do not get per-target builds like gcc does. "bootstrap" means for getting version differences early on in this context, not the targeting. =E2=80=94 Juraj Lutter otis@FreeBSD.org =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D12F81D5-20E3-4275-96FE-F6C258618C19>