ERR#78 'function not implemented'

[Daniel Braniss]

> On 22 May 2019, at 16:48, Konstantin Belousov <kostikbel at gmail.com> wrote:
> 
> On Wed, May 22, 2019 at 06:16:03AM -0700, Enji Cooper wrote:
>> 
>>> On May 22, 2019, at 05:57, Daniel Braniss <danny at cs.huji.ac.il> wrote:
>>> 
>>>> On 22 May 2019, at 11:38, Andrey V. Elsukov <bu7cher at yandex.ru> wrote:
>>>> 
>>>> On 21.05.2019 19:03, Daniel Braniss wrote:
>>>>> Hi,
>>>>> Im using a freebsd-stable-11.1-STABLE to cross compile for arm,  I have been doing it for some time
>>>>> without any issues, but today I decided to try out release.sh and it failes.
>>>>> I have run the ‘bad’ command:
>>>> 
>>>>> -- UNKNOWN FreeBSD ELF64 SYSCALL 568 --
>>>>> #568()                                           ERR#78 'Function not implemented'
>>>>> SIGNAL 12 (SIGSYS) code=SI_KERNEL
>>>>> process killed, signal = 12 (core dumped)
>>>> 
>>>> Hi,
>>>> 
>>>> Your kernel is too old to be able run this binary. Syscall 568 is
>>>> funlinkat(2), it was introduced in r345982.
>>>> 
>>>> https://svnweb.freebsd.org/base?view=revision&revision=345982
>>>> 
>>> hi,
>>> thanks, so that raises a new question:
>>>   Q: to use release.sh one needs to be running the latest current?
>> 
>> In theory, liblegacy and ITOOLS should be taking care of some of this. A binary is being run from the install which should be run from the system.
>> 
> liblegacy only relevant when your target is the old host system.  It cannot
> help with running binary built on newer system.
> 
>> That being said, you should be running a more recent release of 11.x or stable/11.
> No.
> 
> You cannot run 12 binaries on 11 at all (practically any binary would fail),
> and you cannot run some HEAD binaries on 12.


at the moment, my workaround is to change the mounts (so far in 2 places) to not do a chroot, thus using the system’s mount.
(I still have not succeeded in crating an sd image, it just takes too long :-)

Q: why shouldn’t this be the default?

and now I run away and hide

cheers,
	danny