Date: Sun, 24 Nov 2019 15:22:50 -0800 From: Mark Millard <marklmi@yahoo.com> To: Ben Woods <woodsb02@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org>, FreeBSD ports <freebsd-ports@freebsd.org> Subject: Re: head -r355027 context, poudiere jail constructions with the likes of -a arm64.aarch64 -x : awk: can't open file /sys/param.h Message-ID: <82CE331F-D359-415A-A702-49BF7285D88E@yahoo.com> In-Reply-To: <CAOc73CA3Q=93f2kdd=EUcJtU4aw2Rd8n20uw6ovZ8wb96Y0=XA@mail.gmail.com> References: <364D98C1-727B-4956-A73B-10CFEB8E1A12.ref@yahoo.com> <364D98C1-727B-4956-A73B-10CFEB8E1A12@yahoo.com> <CAOc73CA3Q=93f2kdd=EUcJtU4aw2Rd8n20uw6ovZ8wb96Y0=XA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-Nov-24, at 15:11, Ben Woods <woodsb02 at gmail.com> wrote: > On Sun, 24 Nov 2019 at 1:27 pm, Mark Millard <marklmi@yahoo.com> wrote: > My poudiere jail constructions with the likes of -a arm64.aarch64 -x are > all getting: > > awk: can't open file /sys/param.h > source line number 1 > > Hi Mark, > > I have been getting this same error on amd64 for some time when I use the command below. > # poudriere jail -j 13amd64 -u -m src=/usr/src > > Any ideas what it could be? Not so far. Good to know that cross-building is not part of the required context. I've yet to find a place that might be involved that mixes awk use with an expression generating a file path that could generate /sys/param.h as the path. If this was happening in my prior -r352341 context, I did not notice it. I jumped from there to -r355027 . So I can not effectively narrow the range for when it started based on my activity. === 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?82CE331F-D359-415A-A702-49BF7285D88E>