Date: Tue, 21 Apr 2020 23:05:52 -0700 From: Mark Millard <marklmi@yahoo.com> To: freebsd-arm <freebsd-arm@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: "ARM64TODO: fill_fpregs32" showed up while building armv7 ports via poudriere on aarch64 (head -r359427) Message-ID: <113EADFC-53B1-4B88-B8D6-EEC9E5BF3FE2@yahoo.com> References: <113EADFC-53B1-4B88-B8D6-EEC9E5BF3FE2.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a aarch64 head -r359427 based FreeBSD context.
While building armv7 ports via poudriere-devel on a OverDrive 1000
(cortex-A57 aarch64 head -r359427 FreeBSD context) I got:
[00:24:07] [04] [00:00:00] Building x11/libICE | libICE-1.0.10,1
ARM64TODO: fill_fpregs32[00:24:28] [03] [00:00:22] Finished =
devel/libltdl | libltdl-2.4.6: Success
(poudiere was running on the console.)
devel/gettext-tools and devel/swig30 were also building
at the time.
man arch reports:
QUOTE
aarch64 will support execution of armv6 or armv7 binaries if the =
CPU
implements AArch32 execution state, however armv5 binaries aren't
supported.
END QUOTE
(It is referencing chroot style, not lib32, despite not being
explicit about the distinctions.)
Is the support of armv7 binaries not yet fully true?
Does the "ARM64TODO: fill_fpregs32" notice imply that
there might be problems with what was built?
FYI:
# poudriere jail -jFBSDFSSDjailArmV7 -i
Jail name: FBSDFSSDjailArmV7
Jail version: 13.0-CURRENT
Jail arch: arm.armv7
Jail method: null
Jail mount: /usr/obj/DESTDIRs/clang-armv7-installworld-poud
Jail fs: =20
Jail updated: 2020-04-21 22:05:27
# poudriere ports -l
PORTSTREE METHOD TIMESTAMP PATH
default null 2018-10-05 13:09:56 /usr/ports
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?113EADFC-53B1-4B88-B8D6-EEC9E5BF3FE2>