Re: awk behaviour?

From: Michael Butler via freebsd-current <freebsd-current_at_freebsd.org>
Date: Thu, 29 Jul 2021 12:42:29 -0400
On 7/29/21 6:09 AM, Michael Gmelin wrote:
> 
> 
> On Wed, 28 Jul 2021 16:02:30 -0400
> Ed Maste <emaste_at_freebsd.org> wrote:
> 
>> On Wed, 28 Jul 2021 at 15:15, Michael Butler via freebsd-current
>> <freebsd-current_at_freebsd.org> wrote:
>>>
>>> What prompted the question was my (obviously poor) attempt to debug
>>> and resolve this failure when attempting to build a release for
>>> i386 on an amd64 ..
>>
>> This will be due to my 4e224e4be7c3. I'm not sure exactly what's
>> happening yet, but I can provoke this behaviour if `${PKG_CMD}
>> --version` outputs something other than a single line with the version
>> number.
>>
> 
> Could it be, that the pkg binary isn't installed in $LOCALBASE/sbin/pkg,
> (whatever LOCALBASE is at that point)? This would make pkg --version
> shows its bootstrap message:
> 
>    The package management tool is not yet installed on your system.
>    Do you want to fetch and install it now? [y/N]:
> 
> which could explain the behavior.
> 
> Just speculating...

This is consistent with the behaviour I'm now seeing after the most 
recent patch.

In the chroot environment used by a cross-compilation, there is no 
installed pkg port. When pkg is invoked in the target environment, it 
now waits on the yes/no response,

	imb
Received on Thu Jul 29 2021 - 16:42:29 UTC

Original text of this message