Date: Sat, 4 Jun 2016 10:22:20 -0700 From: Bryan Drewery <bdrewery@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64] Message-ID: <7b911297-0399-573c-8021-8ac7ccf30648@FreeBSD.org> In-Reply-To: <1D3FECB2-D7D9-491E-9BDD-C34436EFB333@dsl-only.net> References: <FE82CBAD-ED55-41A3-9413-34948A9CBC0F@dsl-only.net> <7748cc71-3788-22ae-fcb2-699eae529310@FreeBSD.org> <9A1A624D-9286-4C0F-A435-D590E07C1149@dsl-only.net> <39d3c132-cdac-8c9a-c580-82d18f071699@FreeBSD.org> <1D3FECB2-D7D9-491E-9BDD-C34436EFB333@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --72HF2hvgu1repFASb5FaE97dOefkVoKam Content-Type: multipart/mixed; boundary="KgkfTichcNnhlqTrhJBFI77SV5JEbSUGX" From: Bryan Drewery <bdrewery@FreeBSD.org> To: Mark Millard <markmi@dsl-only.net> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Message-ID: <7b911297-0399-573c-8021-8ac7ccf30648@FreeBSD.org> Subject: Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64] References: <FE82CBAD-ED55-41A3-9413-34948A9CBC0F@dsl-only.net> <7748cc71-3788-22ae-fcb2-699eae529310@FreeBSD.org> <9A1A624D-9286-4C0F-A435-D590E07C1149@dsl-only.net> <39d3c132-cdac-8c9a-c580-82d18f071699@FreeBSD.org> <1D3FECB2-D7D9-491E-9BDD-C34436EFB333@dsl-only.net> In-Reply-To: <1D3FECB2-D7D9-491E-9BDD-C34436EFB333@dsl-only.net> --KgkfTichcNnhlqTrhJBFI77SV5JEbSUGX Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 6/4/2016 12:17 AM, Mark Millard wrote: > On 2016-Jun-2, at 12:36 PM, Bryan Drewery <bdrewery at FreeBSD.org> wro= te: >=20 >> On 6/1/2016 6:39 PM, Mark Millard wrote: >>> while filemon.ko now exists: >>>> # ls -l /boot/*/filemon* >>>> -r-xr-xr-x 1 root wheel 32064 Jun 1 17:59 /boot/kernel/filemon.k= o >>> it does not load: >>>> # kldload -n filemon >>>> kldload: can't load filemon: No such file or directory >>>> # dmesg | grep link_elf >>>> link_elf: symbol elf64_freebsd_sysvec undefined >>> So no WITH_META_MODE=3Dyes yet for powerpc64. >> >> >> Please try this patch: http://dpaste.com/37VP5MD.txt >> >> And once you have filemon loaded please run this basic test script. I= t >> should return no output and a zero exit status. >> >> http://dpaste.com/23NTA0A.txt >> >> Just sh file it. >> >> --=20 >> Regards, >> Bryan Drewery >=20 > Unfortunately other things interfered and I was unable to do this befor= e temporarily losing access to the powerpc and powerpc64 boxes --for what= will probably be weeks or months. >=20 No problem... > So for now it is the end of my native-testing for powerpc64 and powerpc= =2E >=20 > I do not know if anyone else has an appropriate context and willingness= to do this specific test or not. >=20 > For the duration I should still be able to do amd64 -> powerpc64 or pow= erpc cross builds (buildworld buildkernel), although likely with less tim= e and more delay for doing so. >=20 > I am hoping to still have rpi2 access for armv6/v7 native use. But I've= yet to make the soft-float to hard-float leap: I focused primarily on th= e powerpc64 and powerpc use, knowing up front of the pending temporarily-= unavailable status. >=20 >=20 >=20 > Thanks for all the work on the build system by you and others. Original= ly I had a bunch of workarounds in my src.conf files to avoid problems th= at occurred for the likes of a libc++-based, xtoolchain-based so-called "= cross build" (self-hosted), powerpc64 environment (no gcc 4.2.1 and clang= not working for such yet). Far more works implicitly in src.conf files f= or such a context now. >=20 Thanks for all of the testing and feedback! --=20 Regards, Bryan Drewery --KgkfTichcNnhlqTrhJBFI77SV5JEbSUGX-- --72HF2hvgu1repFASb5FaE97dOefkVoKam Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJXUw5MAAoJEDXXcbtuRpfPVGAIAKJEW5Tvv8qBHglkYGTR+baw JGtjE7SkFU9+ww9JPeEi2kgy4ipgBoopXL7o0Ibdclou7CU9KQ/9LX7skkFfangZ jhb7udssQIA/nqAiBjgi+CAo4iGeAPIguuBPSfdh0tjldbLlb8GwrKntdC0I8kKi hsxTL/9Lmoa3/r4NTRwVnPnSmTCLII95hIB38F6ugwmIN9jYCGux4JUqlvpEFKfZ f9Je18nnAQ1FXjgS6LhQDZo0GqLmad7CapBUq/mN8lU24khTEliaughNKSN3VxNc Yvhk9bkNDtkQeFtPn7cRWgoRj6gXNQZ+3YisvprIDkE9e91nQYak4Wi0SQTNmrs= =tGtf -----END PGP SIGNATURE----- --72HF2hvgu1repFASb5FaE97dOefkVoKam--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7b911297-0399-573c-8021-8ac7ccf30648>