Re: Error crosscompiling 14.0-ALPHA1 on amd64 for arm64.aarch64
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 12 Aug 2023 23:29:56 UTC
Mike Karels <mike_at_karels.net> wrote on Date: Sat, 12 Aug 2023 22:17:39 UTC : On 12 Aug 2023, at 15:32, Juraj Lutter wrote: > > Hi, > > > > recent 14.0-ALPHA1 sources is giving an error: > > > > Building /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libssp_nonshared/libssp_nonshared.o > > Building /usr/obj/usr/src/arm64.aarch64/obj-lib32/lib/libgcc_eh/int_util.o > > error: unable to create target: 'No available targets are compatible with triple "armv7-unknown-freebsd14.0-gnueabihf"' > > 1 error generated. > > error: unable to create target: 'No available targets are compatible with triple "armv7-unknown-freebsd14.0-gnueabihf"' > > *** [libssp_nonshared.o] Error code 1 > > > > Commandline: > > make -j`sysctl -n hw.ncpu` WITH_META_MODE=1 TARGET=arm64 TARGET_ARCH=aarch64 buildworld buildkernel > > > > The build runs in clean objdir, src git hash 220427da0e9b2c1d8e964120becc17eb7524e46f > > > > Host runs 14.0-CURRENT 28d2e3b5dedf > > > > Am I missing something obvious? > > Thanks. > > Did the buildworld start out by building a cross-compiler? > > Have you tried without meta mode? With a clean objdir, I don't see how > it would matter, but I'm not sure I've tried it. > > The ALPHA1 builds seem to have worked, but I think they run on arm64. > buildworld buildkernel is always done on amd64 for all the official builds as I understand. No use of quemu is required for this. https://ci.freebsd.org/ allows looking at the build logs and such for the ci build activity, not for the release/snapshot builds. It is ports being turned into packages that has the issue of wanting to avoid qemu use and so that only armv6 builds ports->packages via amd64. https://pkg-status.freebsd.org/?all=1&type=package allows looking at the logs and such for this. === Mark Millard marklmi at yahoo.com