Date: Sat, 25 Jan 2020 20:33:59 +0000 From: John F Carr <jfc@mit.edu> To: William Bulley <web@umich.edu> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: lang/python37 fails to build on RPi2 running 12.1-RELEASE Message-ID: <C9C0D7E8-52F8-41E6-9753-71623AD2D76C@exchange.mit.edu> In-Reply-To: <20200125201956.GG657@dell4> References: <20200125201956.GG657@dell4>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 25, 2020, at 15:19 , William Bulley <web@umich.edu> wrote: >=20 > According to John F Carr <jfc@mit.edu> on Sat, 01/25/20 at 15:12: >>=20 >>> > grep 74 /usr/include/errno.h >>> #define EPROGUNAVAIL 74 /* RPC prog. not avail */ >>=20 >> For process exit codes, as opposed to system call return values, look in= /usr/include/sysexits.h: >>=20 >> #define EX_IOERR 74 /* input/output error */ >>=20 >> These codes are not mandatory but they are conventional. See sysexits(3= ). >=20 > In either case, EPROGUNAVAIL or EX_IOERR, what do these tell me? >=20 > What is preventing the install of lang/python37? >=20 > Is a partition full (in the case of "input/output error")? >=20 > What should I be looking for to allow this port build to complete? >=20 > Regards, >=20 > web... >=20 Is there a more verbose log file elsewhere? I ran "make stage" in lang/pyt= hon37 and the output included this line: copying build/lib.freebsd-13.0-CURRENT-arm64-3.7/_ctypes.so -> /usr/ports/l= ang/python37/work/stage/usr/local/lib/python3.7/lib-dynload If there's an error message around there in the full output, it should tell= you what went wrong.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C9C0D7E8-52F8-41E6-9753-71623AD2D76C>