On 2016-Jun-2, at 12:36 PM, Bryan Drewery <bdrewery at FreeBSD.org> wrote:

> 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.ko
>> 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=yes yet for powerpc64.
> Please try this patch: http://dpaste.com/37VP5MD.txt
> And once you have filemon loaded please run this basic test script.  It
> should return no output and a zero exit status.
> http://dpaste.com/23NTA0A.txt
> Just sh file it.
> -- 
> Regards,
> Bryan Drewery

Unfortunately other things interfered and I was unable to do this before 
temporarily losing access to the powerpc and powerpc64 boxes --for what will 
probably be weeks or months.

So for now it is the end of my native-testing for powerpc64 and powerpc.

I do not know if anyone else has an appropriate context and willingness to do 
this specific test or not.

For the duration I should still be able to do amd64 -> powerpc64 or powerpc 
cross builds (buildworld buildkernel), although likely with less time and more 
delay for doing so.

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 the powerpc64 
and powerpc use, knowing up front of the pending temporarily-unavailable status.

Thanks for all the work on the build system by you and others. Originally I had 
a bunch of workarounds in my src.conf files to avoid problems that 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 for such a context now.

Mark Millard
markmi at dsl-only.net

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to